Systems and methods for configuring and communicating with HVAC devices

ABSTRACT

A sensor in a building HVAC system includes a transducer configured to measure a variable in the building HVAC system and to generate a sensor reading indicating a value of the measured variable. The sensor includes a communications interface configured to provide the sensor reading to a control device in the building HVAC system and a near field communication (NFC) circuit separate from the communications interface. The NFC circuit is configured to facilitate bidirectional NFC data communications between the sensor and a mobile device. The sensor includes a processing circuit having a processor and memory. The processing circuit is configured to wirelessly transmit data stored in the memory of the sensor to the mobile device via the NFC circuit, wirelessly receive data from the mobile device via the NFC circuit, and store the data received from the mobile device in the memory of the sensor.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of application Ser. No. 16/362,004,filed Mar. 22, 2019, which is a continuation of application Ser. No.15/183,699, filed Jun. 15, 2016, now U.S. Pat. No. 10,291,292, which isa continuation-in-part of application Ser. No. 14/475,318, filed Sep. 2,2014, now U.S. Pat. No. 9,732,977. The entire disclosures of all ofthese applications and patents are incorporated by reference herein.

BACKGROUND

The present disclosure relates generally to the field of controlequipment such as actuators, sensors, controllers, and other types ofdevices that can be used for monitoring or controlling an automatedsystem or process. The present disclosure relates more particularly tosystems and methods for configuring and communicating with controlequipment in a building automation system.

A building automation system (BAS) is, in general, a system of devicesconfigured to control, monitor, and manage equipment in or around abuilding or building area. A BAS can include a heating, ventilation, andair conditioning (HVAC) system, a security system, a lighting system, afire alerting system, another system that is capable of managingbuilding functions or devices, or any combination thereof. BAS devicescan be installed in any environment (e.g., an indoor area or an outdoorarea) and the environment can include any number of buildings, spaces,zones, rooms, or areas. A BAS can include METASYS building controllersor other devices sold by Johnson Controls, Inc., as well as buildingdevices and components from other sources.

A BAS can include one or more computer systems (e.g., servers, BAScontrollers, etc.) that serve as enterprise level controllers,application or data servers, head nodes, master controllers, or fieldcontrollers for the BAS. Such computer systems can communicate withmultiple downstream building systems or subsystems (e.g., an HVACsystem, a security system, etc.) according to like or disparateprotocols (e.g., LON, BACnet, etc.). The computer systems can alsoprovide one or more human-machine interfaces or client interfaces (e.g.,graphical user interfaces, reporting interfaces, text-based computerinterfaces, client-facing web services, web servers that provide pagesto web clients, etc.) for controlling, viewing, or otherwise interactingwith the BAS, its subsystems, and devices. A BAS can include varioustypes of controllable equipment (e.g., chillers, boilers, air handlingunits, dampers, motors, actuators, pumps, fans, etc.) that can be usedto achieve a desired environment, state, or condition within acontrolled space.

In some BAS implementations, it can be desirable to arrange two or moreactuators in tandem (e.g., in a master-slave configuration).Conventional actuators generally include a physical switch (e.g., adetent potentiometer) attached to the actuator for configuring theactuator to operate as either the master or the slave in a master-slaveconfiguration. It can be challenging to properly configuretandem-mounted actuators, especially when access to the actuators isrestricted or when the proper master-slave configuration is unclear.

Other types of control equipment also generally require physical accessto the equipment for various activities such as commissioning,programming, setting addresses, installing firmware, performingdiagnostics, and/or reading a current operating status. For example,physical access to the circuit board of a control device can be requiredto program the device. It can be difficult to access control devicesthat are mounted in a confined space or sealed from the externalenvironment.

SUMMARY

One implementation of the present disclosure is an actuator in a HVACsystem. The actuator includes a mechanical transducer, an input dataconnection, a feedback data connection, and a processing circuit. Theprocessing circuit is configured to use a master-slave detection signalcommunicated via the feedback data connection to select an operatingmode for the actuator from a set of multiple potential operating modesincluding a master operating mode and a slave operating mode. Theprocessing circuit is configured to operate the mechanical transducer inresponse to a control signal received via the input data connectionaccording to the selected operating mode.

In some embodiments, the processing circuit is configured to generatethe master-slave detection signal and to output the master-slavedetection signal via the feedback data connection.

In some embodiments, the processing circuit is configured to monitor thefeedback data connection for a reply signal from another actuator. Thereply signal can be generated by the other actuator in response toreceiving the output master-slave detection signal. The processingcircuit can be configured to select the master operating mode inresponse to detecting the reply signal from the other actuator at thefeedback data connection.

In some embodiments, the processing circuit is configured to monitor theinput data connection for the master-slave detection signal. Themaster-slave detection signal can be generated by another actuator. Theprocessing circuit can be configured to select the slave operating modein response to detecting the master-slave detection signal from theother actuator at the input data connection.

In some embodiments, the processing circuit is configured to generate areply signal in response to detecting the master-slave detection signalat the input data connection. The processing circuit can be configuredto output the reply signal via the input data connection.

In some embodiments, the processing circuit is configured to monitor theinput data connection for the master-slave detection signal and tomonitor the feedback data connection for a reply signal. The processingcircuit can be configured to select a normal operating mode in responseto a determination that the master-slave detection signal is notdetected at the input data connection and the reply signal is notdetected at the feedback data connection.

In some embodiments, the processing circuit is configured to engage inbi-directional communications with another actuator via the feedbackdata connection. The feedback data connection can be connected with aninput data connection of the other actuator.

In some embodiments, the processing circuit is configured to engage inbi-directional communications with another actuator via the input dataconnection. The input data connection can be connected with a feedbackdata connection of the other actuator.

In some embodiments, the actuator further includes memory storinginstructions for generating the master-slave detection signal. Theprocessing circuit can generate the master-slave detection signalaccording to the stored instructions. In some embodiments, themaster-slave detection signal includes a series of digital pulses.

In some embodiments, the processing circuit includes a master detectioncircuit configured to monitor the input data connection for themaster-slave detection signal, to generate a reply signal in response todetecting the master-slave detection signal at the input dataconnection, and to output the reply signal via the input dataconnection. In some embodiments, the processing circuit includes a slavedetection circuit configured to generate the master-slave detectionsignal, to output the master-slave detection signal via the feedbackdata connection, and to monitor the feedback data connection for thereply signal.

Another implementation of the present disclosure is an actuator in aHVAC system. The actuator includes a mechanical transducer and aprocessing circuit having a processor and memory. The processing circuitis configured to operate the mechanical transducer according to acontrol program stored in the memory. The actuator further includes awireless transceiver configured to facilitate bidirectional wirelessdata communications between the processing circuit and an externaldevice. The actuator further includes a power circuit configured to drawpower from a wireless signal received via the wireless transceiver andto power the processing circuit and the wireless transceiver using thedrawn power. The processing circuit is configured to use the power drawnfrom the wireless signal to wirelessly transmit data stored in thememory of the actuator to the external device via the wirelesstransceiver, to wirelessly receive data from the external device via thewireless transceiver, and to store the data received from the externaldevice in the memory of the actuator.

In some embodiments, the external device is a mobile device. Thebidirectional wireless data communications between the processingcircuit and the external device can include direct communicationsbetween the wireless transceiver of the actuator and a wirelesstransceiver of the mobile device.

In some embodiments, the processing circuit is configured to wirelesslyexchange data with the external device without requiring any wired poweror data connections to the actuator. In some embodiments, the processingcircuit is configured to wirelessly exchange data with the externaldevice while the actuator is contained within packaging that preventsphysical access to the actuator.

In some embodiments, the data received from the external device includesfirmware for the actuator. The firmware can include the control programused by the processing circuit to operate the mechanical transducer. Thecontrol program can include logic for operating the mechanicaltransducer based on variable configuration parameters separate from thecontrol program.

In some embodiments, at least one of the data transmitted to theexternal device and the data received from the external device includeconfiguration parameters for the actuator.

In some embodiments, the processing circuit is capable of operatingmultiple different actuator models. The data received from the externaldevice can include model identification parameters identifying aparticular actuator model and defining configuration settings specificto the identified actuator model. The processing circuit can use themodel identification parameters to operate the actuator according toconfiguration settings specific to the identified actuator model.

In some embodiments, the processing circuit is configured to perform anactuator diagnostic test and to generate diagnostic information as aresult of the test. The data transmitted to the external device caninclude the diagnostic information generated by the processing circuit.

In some embodiments, the external device is another actuator and atleast one of the data transmitted to the external device and the datareceived from the external device include a master-slave detectionsignal. The processing circuit can be configured to use the master-slavedetection signal to select an operating mode for the actuator from a setof multiple potential operating modes including a master operating modeand a slave operating mode

Those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the detailed description set forth herein and taken inconjunction with the accompanying drawings.

Another implementation of the present disclosure is a sensor in abuilding HVAC system. The sensor includes a transducer configured tomeasure a variable in the building HVAC system and to generate a sensorreading indicating a value of the measured variable. The sensor includesa communications interface configured to provide the sensor reading to acontrol device in the building HVAC system and a near fieldcommunication (NFC) circuit separate from the communications interface.The NFC circuit is configured to facilitate bidirectional NFC datacommunications between the sensor and a mobile device. The sensorincludes a processing circuit having a processor and memory. Theprocessing circuit is configured to wirelessly transmit data stored inthe memory of the sensor to the mobile device via the NFC circuit,wirelessly receive data from the mobile device via the NFC circuit, andstore the data received from the mobile device in the memory of thesensor.

In some embodiments, the processing circuit is configured to wirelesslyexchange data with the mobile device while the processing circuit iscontained within packaging that prevents physical access to theprocessing circuit.

In some embodiments, the communications interface is a wirelesscommunications interface.

In some embodiments, the communications interface operates using acommunications protocol that is not NFC and transmits a data setdifferent than the data set communicated via NFC.

In some embodiments, the NFC circuit includes a wireless transceiverconfigured to facilitate bidirectional wireless data communicationsbetween the processing circuit and an external device. The NFC circuitcan include a power circuit configured to draw power from a wirelesssignal received via the wireless transceiver and to power the processingcircuit and the wireless transceiver using the drawn power. Theprocessing circuit is configured to use the power drawn from thewireless signal to wirelessly transmit data stored in the memory of theactuator to the external device via the wireless transceiver, towirelessly receive data from the external device via the wirelesstransceiver, and to store the data received from the external device inthe memory of the actuator.

In some embodiments, the processing circuit is configured to operate ina low-power mode. The NFC circuit is configured to transmit a wake-upsignal to the processing circuit to cause the processing circuit to exitthe low-power mode.

In some embodiments, the processing circuit is capable of operatingmultiple different sensor models. The data received from the externaldevice includes model identification parameters identifying a particularsensor model and defining configuration settings specific to theidentified sensor model. The processing circuit uses the modelidentification parameters to operate the sensor according toconfiguration settings specific to the identified actuator model.

In some embodiments, the mobile device runs an application configured tofacilitate the bidirectional NFC data communications between the sensorand the mobile device.

Another implementation of the present disclosure is a building device.The building device includes a mechanical transducer and a processingcircuit having a processor and memory. The processing circuit isconfigured to operate the mechanical transducer according to a controlprogram stored in the memory. The building device further includes anear field communication (NFC) circuit configured to facilitatebidirectional NFC data communications between the building device and amobile device. The processing circuit is configured to wirelesslytransmit data stored in the memory of the building device to the mobiledevice via the NFC circuit, wirelessly receive data from the mobiledevice via the NFC circuit, and store the data received from the mobiledevice in the memory of the building device.

In some embodiments, the processing circuit is configured to wirelesslyexchange data with the mobile device while the processing circuit iscontained within packaging that prevents physical access to theprocessing circuit.

In some embodiments, the communications interface is a wirelesscommunications interface.

In some embodiments, the communications interface operates using acommunications protocol that is not NFC and transmits a data setdifferent than the data set communicated via NFC.

In some embodiments, the NFC circuit includes a wireless transceiverconfigured to facilitate bidirectional wireless data communicationsbetween the processing circuit and an external device. The NFC circuitcan include a power circuit configured to draw power from a wirelesssignal received via the wireless transceiver and to power the processingcircuit and the wireless transceiver using the drawn power. Theprocessing circuit is configured to use the power drawn from thewireless signal to wirelessly transmit data stored in the memory of theactuator to the external device via the wireless transceiver, towirelessly receive data from the external device via the wirelesstransceiver, and to store the data received from the external device inthe memory of the actuator.

In some embodiments, the processing circuit is configured to operate ina low-power mode. The NFC circuit is configured to transmit a wake-upsignal to the processing circuit to cause the processing circuit to exitthe low-power mode.

In some embodiments, the processing circuit is capable of operatingmultiple different building device models. The data received from theexternal device includes model identification parameters identifying aparticular building device model and defining configuration settingsspecific to the identified building device model. The processing circuituses the model identification parameters to operate the building deviceaccording to configuration settings specific to the identified actuatormodel.

In some embodiments, the mobile device runs an application configured tofacilitate the bidirectional NFC data communications between thebuilding device and the mobile device.

Another implementation of the present disclosure is a method forconfiguring and communicating with a building device. The methodincludes establishing a bidirectional near field communications (NFC)link between the building device and a mobile device via a NFC circuitof the building device, wirelessly transmitting data stored in a memoryof the building device to the mobile device via the NFC circuit,wirelessly receiving data from the mobile device via the NFC circuit,and storing the data received from the mobile device in the memory ofthe building device.

In some embodiments, the data stored in a memory of the building deviceand wirelessly transmitted to the mobile device via the NFC circuitincludes an access log entry. The log entry includes one of a timestamp,a tag identification number, a configuration parameter, a type of actionperformed, and a troubleshooting message.

In some embodiments, the data wirelessly received from the mobile devicevia the NFC circuit, and stored in the memory of the building deviceincludes configuration parameters associated with the building device.

In some embodiments, method further includes transmitting to anotherdevice data received by the mobile device from the building device viathe NFC circuit.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of a building serviced by a HVAC system,according to some embodiments.

FIG. 2 is a block diagram illustrating a portion of the HVAC system ofFIG. 1 in greater detail, according to some embodiments.

FIG. 3 is a block diagram illustrating multiple actuators of the HVACsystem of FIG. 1 arranged in tandem, according to some embodiments.

FIG. 4 is a block diagram illustrating the actuators of FIG. 3 ingreater detail, according to some embodiments.

FIG. 5 is a block diagram illustrating a first process for automaticallydetecting an actuator arrangement and setting an actuator operating modein which a master actuator initiates the process, according to someembodiments.

FIG. 6 is a block diagram illustrating a second process forautomatically detecting an actuator arrangement and setting an actuatoroperating mode in which a slave actuator initiates the process,according to some embodiments.

FIG. 7A is a block diagram illustrating the master actuator and slaveactuator of FIGS. 3-5 in greater detail, according to some embodiments.

FIG. 7B is a circuit diagram illustrating selected portions of themaster actuator and the slave of FIG. 7A, according to some embodiments.

FIG. 8 is a flowchart of a process for automatically selecting anoperating mode for a HVAC actuator, according to some embodiments.

FIG. 9 is a flowchart of another process for automatically selecting anoperating mode for a HVAC actuator, according to some embodiments.

FIG. 10 is a flowchart of yet another process for automaticallyselecting an operating mode for a HVAC actuator, according to someembodiments.

FIG. 11 is a block diagram of an actuator configured to wirelesslycommunicate with an external device without requiring any wired power ordata connections to the actuator, according to some embodiments.

FIG. 12 is flowchart of a process for wirelessly configuring andcommunicating with an actuator in a HVAC system, according to someembodiments.

FIG. 13 is a block diagram of a building device configured tocommunicate with an external device via near field communication,according to some embodiments.

FIG. 14 is a detailed block diagram of an NFC circuit for the buildingdevice of FIG. 13, according to some embodiments.

FIGS. 15A-15H are drawings of a graphical user interface provided by anapplication running on a mobile device for facilitating communicationswith the building device via NFC, according to some embodiments.

FIG. 16 is a flowchart of a process for configuring and communicatingwith a building device via NFC, according to some embodiments.

DETAILED DESCRIPTION

Referring generally to the FIGURES, systems and methods for configuringand communicating with HVAC devices are shown, according to variousexemplary embodiments. The systems and methods described herein can beused to automatically select and set an operating mode (e.g., master,slave, normal, etc.) for actuators in a HVAC system. The systems andmethods described herein can also be used to wirelessly configure,control, exchange data, or otherwise wirelessly communicate with anactuator in a HVAC system.

Actuators include any apparatus capable of providing forces and/ormotion in response to a control signal. Actuators can use any of avariety of force transducers such as rotary motors, linear motors,hydraulic or pneumatic pistons/motors, piezoelectric elements, relays,comb drives, thermal bimorphs, or other similar devices to providemechanical motion. An actuator can provide any combination of linear,curved, or rotary forces/motion. Some actuators use rotary motors toprovide circular motion and/or linear motion (e.g., via a screw drive).Other actuators use linear motors to provide linear motion.

Actuators can include a variety of mechanical components such as gears,pulleys, cams, screws, levers, crankshafts, ratchets, or othercomponents capable of changing or affecting the motion provided by theactuating/transducing element. In some embodiments, actuators do notproduce significant motion in operation. For example, some actuators canbe operated to exert a force or torque to an external element (e.g., aholding force) without affecting significant linear or rotary motion.

In some implementations, multiple actuators can be interconnected in atandem arrangement. The actuators can be identical or substantiallyidentical (e.g., the same manufacturer, model, combination ofcomponents, etc.). For example, each actuator can have an input dataconnection, a feedback data connection, and the same or similar internalprocessing components. Each actuator can be capable of operating inmultiple different operating modes (e.g., as a master actuator, as aslave actuator, in a normal operating mode, etc.). The systems andmethods of the present disclosure can be used to automatically identifyand configure one of the actuators as a master actuator and one or moreof the actuators as slave actuators based on the manner in which theactuators are interconnected.

In an exemplary arrangement, the input data connection of a firstactuator can be connected (e.g., via a communications bus) to the outputof a controller that provides a control signal to the first actuator.The other actuators can be arranged in tandem with the first actuator.For example, the feedback data connection of the first actuator can beconnected to the input data connection of a second actuator. In someembodiments, the second actuator can be arranged in parallel with one ormore additional actuators. For example, the feedback data connection ofthe first actuator can be connected with both the input data connectionof the second actuator and the input data connections of the one or moreadditional actuators. In this exemplary arrangement, it would bedesirable to identify the first actuator as a master actuator and theother actuators as slave actuators.

Each actuator can be configured to generate a master-slave detectionsignal (e.g., an analog or digital signal protocol) and to output themaster-slave detection signal via its feedback data connection. In someembodiments, the master-slave detection signal is generated and outputby an actuator when the actuator first receives power. If the feedbackdata connection of the actuator is connected with the input dataconnection of another actuator, the master-slave detection signal willbe received at the input data connection of the other actuator.

Each actuator can be configured to monitor its input data connection forthe master-slave detection signal. If an actuator detects themaster-slave detection signal at its input data connection, the actuatorcan determine that it is arranged in a slave configuration (i.e., itsinput data connection is connected with the feedback data connection ofanother actuator) and can automatically configure itself to operate in aslave operating mode. In response to detecting the master-slavedetection signal at its input data connection, the slave actuator cangenerate and output a reply signal. The slave actuator can output thereply signal via its input data connection.

Each actuator can be configured to monitor its feedback data connectionfor the reply signal. If an actuator detects the reply signal at itsfeedback data connection, the actuator can determine that it is arrangedin a master configuration (i.e., its feedback data connection isconnected with the input data connection of another actuator) and canautomatically configure itself to operate in a master operating mode.The master actuator and the slave actuator can engage in bidirectionaldata communications via a communications bus connecting the feedbackdata connection of the master actuator with the input data connection ofthe slave actuator.

In some embodiments, if an actuator does not detect the master-slavedetection signal at its input data connection and does not detect thereply signal at its feedback data connection, the actuator can determinethat it is not arranged in either a master configuration or a slaveconfiguration (i.e., it is not connected with any other actuators) andcan automatically configure itself to operate in a normal operatingmode.

Each actuator can have a mode indicator (e.g., a light, a speaker, anelectronic display, etc.) to indicate the operating mode in which theactuator is configured. For example, if the mode indicator is a LED, theLED can be illuminated to indicate that the actuator is operating in themaster operating mode. The LED can flash, blink, or illuminate adifferent color to indicate that the actuator is operating in the slaveoperating mode. The LED can turn off or illuminate yet a different colorto indicate that the actuator is operating in the normal operating mode.

In some embodiments, an actuator can be configured to wirelesslycommunicate with an external device (e.g., a mobile device, acontroller, another actuator, etc.) to send and receive various types ofdata related to the operation of the actuator (e.g., firmware data,control logic, model identification parameters, configurationparameters, diagnostic data, etc.). Advantageously, the actuator cancommunicate with the external device without requiring any wired poweror data connections to the actuator. This allows the actuator to sendand receive data in the event that physical access to the actuator islimited. For example, the actuator can be installed in a location thatis not readily accessible by a user or service technician.

In some embodiments, the actuator can communicate with external deviceswhile the actuator is still in its packaging at a manufacturer facilityor a distributor location. The actuator can be constructed and packagedas a generic actuator and subsequently configured with suitablefirmware, software, configuration parameters, or other data specific toa particular actuator model and/or implementation. Operational data suchas end of line test data or other diagnostic data can be extracted fromthe actuator without requiring a physical data connection.

HVAC System and Operating Environment

Referring now to FIG. 1, a perspective view of a building 10 is shown.Building 10 is serviced by a heating, ventilation, and air conditioningsystem (HVAC) system 20. HVAC system 20 is shown to include a chiller22, a boiler 24, a rooftop cooling unit 26, and a plurality of airhandling units (AHUs) 36. HVAC system 20 uses a fluid circulation systemto provide heating and/or cooling for building 10. The circulated fluidcan be cooled in chiller 22 or heated in boiler 24, depending on whethercooling or heating is required. Boiler 24 can add heat to the circulatedfluid by burning a combustible material (e.g., natural gas). Chiller 22can place the circulated fluid in a heat exchange relationship withanother fluid (e.g., a refrigerant) in a heat exchanger (e.g., anevaporator). The refrigerant removes heat from the circulated fluidduring an evaporation process, thereby cooling the circulated fluid.

The circulated fluid from chiller 22 or boiler 24 can be transported toAHUs 36 via piping 32. AHUs 36 can place the circulated fluid in a heatexchange relationship with an airflow passing through AHUs 36. Forexample, the airflow can be passed over piping in fan coil units orother air conditioning terminal units through which the circulated fluidflows. AHUs 36 can transfer heat between the airflow and the circulatedfluid to provide heating or cooling for the airflow. The heated orcooled air can be delivered to building 10 via an air distributionsystem including air supply ducts 38 and can return to AHUs 36 via airreturn ducts 40. HVAC system 20 is shown to include a separate AHU 36 oneach floor of building 10. In other embodiments, a single AHU (e.g., arooftop AHU) can supply air for multiple floors or zones. The circulatedfluid from AHUs 36 can return chiller 22 or boiler 24 via piping 34.

In some embodiments, the refrigerant in chiller 22 is vaporized uponabsorbing heat from the circulated fluid. The vapor refrigerant can beprovided to a compressor within chiller 22 where the temperature andpressure of the refrigerant are increased (e.g., using a rotatingimpeller, a screw compressor, a scroll compressor, a reciprocatingcompressor, a centrifugal compressor, etc.). The compressed refrigerantcan be discharged into a condenser within chiller 22. In someembodiments, water (or another chilled fluid) flows through tubes in thecondenser of chiller 22 to absorb heat from the refrigerant vapor,thereby causing the refrigerant to condense. The water flowing throughtubes in the condenser can be pumped from chiller 22 to a rooftopcooling unit 26 via piping 28. Cooling unit 26 can use fan drivencooling or fan driven evaporation to remove heat from the water. Thecooled water in rooftop unit 26 can be delivered back to chiller 22 viapiping 30 and the cycle repeats.

Referring now to FIG. 2, a block diagram of a portion of HVAC system 20is shown, according to some embodiments. In FIG. 2, AHU 36 is shown asan economizer type air handling unit. Economizer type air handling unitsvary the amount of outside air and return air used by the air handlingunit for heating or cooling. For example, AHU 36 can receive return air82 from building 10 via return air duct 40 and can deliver supply air 86to building 10 via supply air duct 38. AHU 36 can be configured tooperate exhaust air damper 60, mixing damper 62, and outside air damper64 to control an amount of outside air 80 and return air 82 that combineto form supply air 86. Any return air 82 that does not pass throughmixing damper 62 can be exhausted from AHU 36 through exhaust damper 60as exhaust air 84.

Each of dampers 60-64 can be operated by an actuator. As shown in FIG.2, exhaust air damper 60 can be operated by actuator 54, mixing damper62 can be operated by actuator 56, and outside air damper 64 can beoperated by actuator 58. Actuators 54-58 can communicate with an AHUcontroller 44 via a communications link 52. AHU controller 44 can be aneconomizer controller configured to use one or more control algorithms(e.g., state-based algorithms, extremum seeking control algorithms, PIDcontrol algorithms, model predictive control algorithms, etc.) tocontrol actuators 54-58. Actuators 54-58 can receive control signalsfrom AHU controller 44 and can provide feedback signals to AHUcontroller 44. Feedback signals can include, for example, an indicationof a current actuator position, an amount of torque or force exerted bythe actuator, diagnostic information (e.g., results of diagnostic testsperformed by actuators 54-58), status information, commissioninginformation, configuration settings, calibration data, and/or othertypes of information or data that can be collected, stored, or used byactuators 54-58.

Still referring to FIG. 2, AHU 36 is shown to include a cooling coil 68,a heating coil 70, and a fan 66. In some embodiments, cooling coil 68,heating coil 70, and fan 66 are positioned within supply air duct 38.Fan 66 can be configured to force supply air 86 through cooling coil 68and/or heating coil 70. AHU controller 44 can communicate with fan 66via communications link 78 to control a flow rate of supply air 86.Cooling coil 68 can receive a chilled fluid from chiller 22 via piping32 and can return the chilled fluid to chiller 22 via piping 34. Valve92 can be positioned along piping 32 or piping 34 to control an amountof the chilled fluid provided to cooling coil 68. Heating coil 70 canreceive a heated fluid from boiler 24 via piping 32 and can return theheated fluid to boiler 24 via piping 34. Valve 94 can be positionedalong piping 32 or piping 34 to control an amount of the heated fluidprovided to heating coil 70.

Each of valves 92-94 can be controlled by an actuator. As shown in FIG.2, valve 92 can be controlled by actuator 88 and valve 94 can becontrolled by actuator 90. Actuators 88-90 can communicate with AHUcontroller 44 via communications links 96-98. Actuators 88-90 canreceive control signals from AHU controller 44 and can provide feedbacksignals to controller 44. In some embodiments, AHU controller 44receives a measurement of the supply air temperature from a temperaturesensor 72 positioned in supply air duct 38 (e.g., downstream of coolingcoil 68 and heating coil 70). AHU controller 44 can operate actuators88-90 to modulate an amount of heating or cooling provided to supply air86 to achieve a setpoint temperature for supply air 86 or to maintainthe temperature of supply air 86 within a setpoint temperature range.

In some embodiments, two or more of actuators 54-58 and/or actuators88-90 can be arranged in a tandem configuration. For example, oneactuator can be arranged as a master actuator (e.g., directly connectedwith AHU controller 44) and other actuators can be arranged as slaveactuators (e.g., connected to a feedback data connection of the masteractuator). Such a tandem arrangement is described in greater detail withreference to FIG. 3. Advantageously, each of actuators 54-58 and 88-90can be configured to automatically determine whether it is arranged as amaster actuator, a slave actuator, or not linked to any other actuators.Each of actuators 54-58 and 88-90 can be configured to automatically setits own operating mode (e.g., master, slave, non-linked, etc.) based onthe determined arrangement.

Still referring to FIG. 2, HVAC system 20 is shown to include asupervisory controller 42 and a client device 46. Supervisory controller42 can include one or more computer systems (e.g., servers, BAScontrollers, etc.) that serve as enterprise level controllers,application or data servers, head nodes, master controllers, or fieldcontrollers for HVAC system 20. Supervisory controller 42 cancommunicate with multiple downstream building systems or subsystems(e.g., an HVAC system, a security system, etc.) via a communicationslink 50 according to like or disparate protocols (e.g., LON, BACnet,etc.). In some embodiments, AHU controller 44 receives information(e.g., commands, setpoints, operating boundaries, etc.) from supervisorycontroller 42. For example, supervisory controller 42 can provide AHUcontroller 44 with a high fan speed limit and a low fan speed limit. Alow limit can avoid frequent component and power taxing fan start-upswhile a high limit can avoid operation near the mechanical or thermallimits of the fan system. In various embodiments, AHU controller 44 andsupervisory controller 42 can be separate (as shown in FIG. 2) orintegrated. In an integrated implementation, AHU controller 44 can be asoftware module configured for execution by a processor of supervisorycontroller 42.

Client device 46 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 20, its subsystems,and/or devices. Client device 46 can be a computer workstation, a clientterminal, a remote or local interface, or any other type of userinterface device. Client device 46 can be a stationary terminal or amobile device. For example, client device 46 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.

Automated Master-Slave Determination and Operating Mode Selection

Referring now to FIG. 3, a block diagram illustrating a portion of HVACsystem 20 is shown, according to some embodiments. HVAC system 20 isshown to include a controller 100 and several actuators 102, 104, and106 in a tandem arrangement. Controller 100 can be an AHU controller(e.g., AHU controller 44), an economizer controller, a supervisorycontroller (e.g., supervisory controller 42), a zone controller, a fieldcontroller, an enterprise level controller, a motor controller, anequipment-level controller (e.g., an actuator controller) or any othertype of controller that can be used in HVAC system 20.

Controller 100 is shown to include an output data connection 120 and aninput data connection 122. Controller 100 can provide a control signalfor actuators 102-106 via output data connection 120. In someembodiments, the control signal provided via output data connection 120is a voltage signal. Controller 100 can modulate the voltage signalwithin a voltage range (e.g., 0-10 VDC) to set a rotational position foractuators 102-106. For example, a voltage of 0.0 VDC may correspond to 0degrees of rotation and a voltage of 10.0 VDC may correspond to 90degrees of rotation. The control signal can be communicated to actuators102-106 via a communications bus 124 connected to output data connection120.

Actuators 102-106 can provide controller 100 with a feedback signalindicating the current rotational position of actuators 102-106. Thefeedback signal can be a voltage signal similar to the control signaloutput by controller 100 (e.g., 0-10 VDC) and can be communicated tocontroller 100 via communications bus 126. Controller 100 can receivethe feedback signal at input data connection 122. In some embodiments,the feedback signal includes an amount of torque or force exerted byactuators 102-106, diagnostic information (e.g., results of diagnostictests performed by actuators 54-58), status information, commissioninginformation, configuration settings, calibration data, and/or othertypes of information or data that can be collected, stored, or used byactuators 102-106.

Actuators 102-106 can be any actuators of HVAC system 20. For example,actuators 102-106 can be damper actuators (e.g., actuators 54-58), valveactuators (e.g., actuators 88-90), fan actuators, pump actuators, or anyother type of actuators that can be used in HVAC system 20. In variousembodiments, actuators 102-106 can be linear proportional actuators(i.e., the rotational position of actuators 102-106 is proportional tothe voltage provided by controller 100) or non-linear actuators (i.e.,the rotational position of actuators 102-106 varies disproportionatelywith the voltage provided by controller 100).

In some embodiments, actuators 102-106 are identical or substantiallyidentical (e.g., the same manufacturer, the same model, the sameinternal components, etc.). For example, each of actuators 102-106 isshown to include an input data connection (i.e., input data connections108, 110, and 112) and a feedback data connection (i.e., feedback dataconnections 114, 116, and 118). Actuators 102-106 can have the same orsimilar internal processing components (e.g., a processing circuithaving a processor, memory, and memory modules). Each of actuators102-106 can be capable of operating in multiple different operatingmodes. For example, each of actuators 102-106 can be capable ofoperating as a master actuator, as a slave actuator, or in a normal(e.g., non-linked) operating mode. Advantageously, each of actuators102-106 can be configured to automatically identify itself as a masteractuator, a slave actuator, or a non-linked actuator and can set its ownoperating mode based on the manner in which it is interconnected withthe other actuators.

Still referring to FIG. 3, actuators 102-106 are shown in a tandemarrangement, according to some embodiments. In the exemplary tandemarrangement, input data connection 108 of actuator 102 is connected(e.g., via communications bus 124) to output data connection 120 ofcontroller 100. Feedback data connection 114 of actuator 102 can beconnected to input data connection 110 of actuator 104 viacommunications bus 128. Communications bus 128 can be a wired orwireless communications link and can use any of a variety of disparatecommunications protocols (e.g., BACnet, LON, WiFi, Bluetooth, NFC,TCP/IP, etc.). Actuator 104 can be arranged in parallel with actuator106. For example, feedback data connection 114 of actuator 102 can beconnected with both input data connection 110 of actuator 104 and inputdata connection 112 of actuator 106 via communications bus 128.

As shown in FIG. 3, actuator 102 is arranged as a master actuator andactuators 104-106 are arranged as slave actuators. A master actuator canbe defined as an actuator having an input data connection that isconnected to the output data connection of a controller. The feedbackdata connection of a master actuator can be connected with the inputdata connections of one or more slave actuators. A slave actuator can bedefined as an actuator having an input data connection that is connectedto the feedback data connection of a master actuator. The feedback dataconnection of a slave actuator can be connected to the input dataconnection of the controller or may not be connected with anything.

Referring now to FIG. 4, a block diagram illustrating actuators 102 and104 in greater detail is shown, according to some embodiments. FIG. 4illustrates another tandem configuration in which actuator 102 isarranged as a master actuator and actuator 104 is arranged as a slaveactuator. In FIG. 4, output data connection 120 of controller 100 isconnected with input data connection 108 of actuator 102 viacommunications bus 124. Feedback data connection 114 of actuator 102 canbe connected with input data connection 110 of actuator 104 via abidirectional communications link 228. Bidirectional communications link228 can be implemented as a communications bus (e.g., communications bus128), a wired communications interface, or a wireless communicationsinterface. Bidirectional communications link 228 and can utilize any ofa variety of disparate communications protocols (e.g., BACnet, LON,TCP/IP, Bluetooth, NFC, WiFi, etc.). Feedback data connection 116 ofactuator 104 can be connected with input data connection 122 ofcontroller 100 via communications bus 126.

Actuators 102 and 104 can be identical or substantially identical andcan include the same or similar internal processing components. Forexample, each of actuators 102-104 is shown to include a processingcircuit 134 including a processor 136 and memory 138. Processor 136 canbe a general purpose or specific purpose processor, an applicationspecific integrated circuit (ASIC), one or more field programmable gatearrays (FPGAs), a group of processing components, or other suitableprocessing components. Processor 136 is configured to execute computercode or instructions stored in memory 138 or received from othercomputer readable media (e.g., CDROM, network storage, a remote server,etc.).

The term “corresponding actuator” is used throughout this description tospecify a particular actuator with respect to a given component. Thecorresponding actuator for any given component is the actuator thatincludes the component. For example, the corresponding actuator for allof the components of actuator 102 is actuator 102, whereas thecorresponding actuator for all of the components of actuator 104 isactuator 104. The same reference numbers are used for many of thecomponents of each actuator to indicate that each actuator can beidentical or substantially identical. Advantageously, each processingcircuit 134 can be configured to automatically determine whether thecorresponding actuator is arranged as a master actuator, a slaveactuator, or in a non-linked arrangement notwithstanding the identicalor substantially identical components of each actuator. Processingcircuit 134 can select an operating mode for the corresponding actuatorbased on a result of the determination.

Memory 138 can include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 138 can include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory138 can include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 138 can be communicably connected toprocessor 136 via processing circuit 134 and can include computer codefor executing (e.g., by processor 136) one or more processes describedherein.

Still referring to FIG. 4, memory 138 is shown to include a feedbackgenerator 140. Each feedback generator 140 can be configured to generatea master-slave detection signal (e.g., a series of digital pulses, ananalog signal, etc.) and to output the master-slave detection signal viathe feedback data connection of the corresponding actuator (e.g.,feedback data connection 114 or 116). In some embodiments, feedbackgenerator 140 generates and outputs the master-slave detection signalwhen the corresponding actuator first receives power. In someembodiments, feedback generator 140 generates and outputs themaster-slave detection signal when the corresponding actuator enters acalibration mode. An actuator can enter the calibration mode, forexample, in response to a signal from another component of HVAC system20 (e.g., a controller, a client device, another actuator, etc.) and/orin response to a user-operable switch of the actuator being moved into acalibration position.

The master-slave detection signal output at feedback data connection 114of actuator 102 can be received at input data connection 110 of actuator104 since feedback data connection 114 is connected with input dataconnection 110 via bidirectional communications link 228. However, themaster-slave detection signal output at feedback data connection 116 maynot be received at input data connection 108 since no direct connectionexists between feedback data connection 116 and input data connection108. This distinction can be used to identify actuator 102 as a masteractuator and to identify actuator 104 as a slave actuator, as describedin greater detail below.

Still referring to FIG. 4, memory 138 is shown to include a mastersignal detector 142. Master signal detector 142 can be configured tomonitor the input data connection of the corresponding actuator for themaster-slave detection signal. In the arrangement shown in FIG. 4, themaster signal detector 142 of actuator 104 can detect the master-slavedetection signal because input data connection 110 is connected with thefeedback data connection of another actuator (i.e., feedback dataconnection 114). However, the master signal detector 142 of actuator 102may not detect the master-slave detection signal because input dataconnection 108 is not directly connected with the feedback dataconnection of any other actuator. In response to detecting themaster-slave detection signal, master signal detector 142 can generate anotification for operating mode selector 144 and/or reply signalgenerator 146. The notification can be an analog or digital signalindicating that the master-slave detection signal has been detected atthe input data connection of the corresponding actuator.

Operating mode selector 144 can be configured to select an operatingmode for the corresponding actuator. If operating mode selector 144receives an input indicating that the master-slave detection signal hasbeen detected at the input data connection of the correspondingactuator, operating mode selector 144 can determine that the actuator isarranged in a slave configuration and can select a slave operating modefor the actuator.

Reply signal generator 146 can be configured to generate and output areply signal. The reply signal can be a series of digital pulses, ananalog signal, or any other type of data signal. In some embodiments,reply signal generator 146 generates and outputs the reply signal inresponse to a determination (e.g., by operating mode selector 144) thatthe actuator is arranged in a slave configuration and/or in response toa selection of the slave operating mode. In some embodiments, replysignal generator 146 generates and outputs the reply signal in responseto receiving an input (e.g., from master signal detector 142) indicatingthat the master-slave detection signal has been detected at the inputdata connection of the corresponding actuator.

In the arrangement shown in FIG. 4, the reply signal generator 146 ofactuator 104 can generate and output a reply signal because themaster-slave detection signal is received and detected at input dataconnection 110. However, the reply signal generator 146 of actuator 102may not generate or output a reply signal because the master-slavedetection signal is not received or detected at input data connection108.

Reply signal generator 146 can output the reply signal via the inputdata connection of the corresponding actuator. The reply signal can becommunicated from the input data connection back to the feedback dataconnection of the actuator from which the master-slave detection signalwas received. For example, the reply signal generated by the replysignal generator 146 of actuator 104 can be output via data connection110 and communicated back to feedback data connection 114 viabidirectional communications link 228. Actuators 102-104 can engage inbidirectional data communications via bidirectional communications link228. For example, actuator 102 can send the master-slave detectionsignal via bidirectional communications link 228 and can receive thereply signal from actuator 104 via bidirectional communications link228.

Still referring to FIG. 4, memory 138 is shown to include a reply signaldetector 148. Reply signal detector 148 can be configured to monitor thefeedback data connection of the corresponding actuator for the replysignal. In the arrangement shown in FIG. 4, the reply signal detector148 of actuator 102 can detect the reply signal that is generated by thereply signal generator in actuator 104 and communicated back to feedbackdata connection 114 of actuator 102. However, the reply signal detector148 of actuator 104 may not detect the reply signal because feedbackdata connection 116 does not receive the reply signal.

In response to detecting the reply signal, reply signal detector 148 cangenerate a notification for operating mode selector 144. Thenotification can be an analog or digital signal indicating that thereply signal has been received at the feedback data connection of thecorresponding actuator. If operating mode selector 144 receives an inputindicating that the reply signal has been received at the feedback dataconnection of the corresponding actuator, operating mode selector 144can determine that the actuator is arranged in a master configurationand can select a master operating mode for the actuator.

In some embodiments, if an actuator does not detect the master-slavedetection signal at its input data connection and does not detect thereply signal at its feedback data connection, operating mode selector144 can determine that the actuator is arranged in neither the masterconfiguration nor the slave configuration. For example, the actuator maynot be connected with any other actuators. In response to adetermination that the actuator is arranged in neither the masterconfiguration nor the slave configuration, operating mode selector 144can select a normal (e.g., non-linked) operating mode.

Actuators 102-104 can behave differently based on whether operating modeselector 144 selects the master operating mode, the slave operatingmode, or the normal operating mode. For example, in the master operatingmode, an actuator can accept an input signal of any value within aninput signal range (e.g., 0-10 VDC) and can produce a feedback signal atone or more discrete values (e.g., 0 VDC, 5 VDC, 10 VDC, etc.). In theslave operating mode, an actuator can accept an input signal at one ormore discrete values (e.g., 0 VDC, 5 VDC, 10 VDC, etc.) and can producea feedback signal of any value within a feedback signal range (e.g.,0-10 VDC). In the normal operating mode, an actuator can accept an inputsignal of any value within an input signal range (e.g., 0-10 VDC) andcan produce a feedback signal of any value within a feedback signalrange (e.g., 0-10 VDC).

Still referring to FIG. 4, memory 138 is shown to include a proportionalinput module 154. Proportional input module 154 can be configured totranslate a control signal received from controller 100 into an amountof rotation, linear motion, force, torque, or other physical outputprovided by transducer 156. For example, proportional input module 154can translate an input voltage of 0.0 VDC to 0 degrees of rotation andcan translate an input voltage of 10.0 VDC to 90 degrees of rotation.The output rotation can be provided to transducer 156 directly fromproportional input module 154 or indirectly (e.g., via feedbackgenerator 140). Feedback generator 140 can include one or more filters(e.g., low pass filters), gain stages, and/or buffers applied to theoutput rotation before the output rotation is communicated as a feedbacksignal to controller 100. Controller 100 can use the feedback signal todetermine the current rotational position of a motor, valve, or dampercontrolled by the actuator.

In some embodiments, actuators 102-106 include a mode indicator 150.Mode indicator 150 can be a light, a speaker, an electronic display, orother component configured to indicate the operating mode selected byoperating mode selector 144. For example, mode indicator 150 can be aLED and can be illuminated to indicate that the actuator is operating inthe master operating mode. The LED can flash, blink, or illuminate adifferent color to indicate that the actuator is operating in the slaveoperating mode. The LED can turn off or illuminate yet a different colorto indicate that the actuator is operating in the normal operating mode.

Referring now to FIGS. 5-6, a pair of block diagrams illustrating twoprocesses 500 and 600 are shown, according to some embodiments.Processes 500 and 600 can be performed by one or more actuators of aHVAC system to automatically identify an arrangement of the actuatorsand to automatically select an operating mode. In both processes 500 and600, a bidirectional communications link 228 is formed between a masteractuator 102 and a slave actuator 104. Bidirectional communications link228 connects the feedback data connection 114 of master actuator 102with the input data connection 110 of slave actuator 104. Bidirectionalcommunications link 228 can be used to exchange various types of databetween actuators 102 and 104. For example, bidirectional communicationslink 228 can be used to communicate a master-slave detection signal, areply signal, diagnostic information, status information, configurationsettings, calibration data, or other types of information or data thatcan be collected, stored, or used by actuators 102-104.

Referring specifically to FIG. 5, process 500 is shown to include masteractuator 102 sending a detection signal to slave actuator 104 viabidirectional communications link 228 (step 502). Actuators 102 and 104can be identical or substantially identical and can be distinguishedonly by the manner in which actuators 102-104 are interconnected. Eitheractuator can be capable of functioning as a master actuator or a slaveactuator. At the time the detection signal is communicated, it can beunknown whether each of actuators 102-104 is arranged as a masteractuator or a slave actuator.

Master actuator 102 can generate the detection signal according tostored criteria and can output the detection signal via feedback dataconnection 114. The detection signal can be a series of digital pulses,an analog signal, or any other type of data signal. Slave actuator 104can monitor input data connection 110 for the detection signal. Slaveactuator 104 can identify the detection signal by comparing the signalsreceived at input data connection 110 with a stored representation ofthe detection signal.

In response to receiving the detection signal at input data connection110, slave actuator 104 can set its operating mode to a slave operatingmode (step 504) and can send a reply signal back to master actuator 102via bidirectional communications link 228 (step 506). Slave actuator 104can generate the reply signal according to stored criteria and canoutput the reply signal via input data connection 110. The reply signalcan be a series of digital pulses, an analog signal, or any other typeof data signal.

Master actuator 102 can monitor feedback data connection 114 for thereply signal. Master actuator 102 can identify the reply signal bycomparing the signals received at feedback data connection 114 with astored representation of the reply signal. In response to receiving thereply signal at feedback data connection 114, master actuator 102 canset its operating mode to a master operating mode (step 508).

In process 500, master actuator 102 initiates the master-slaveidentification process by sending the detection signal to slave actuator104. Slave actuator 104 then responds with the reply signal. In otherembodiments, slave actuator 104 can initiate the process and masteractuator 102 can respond with the reply signal. Such an alternativeprocess is illustrated in FIG. 6.

Referring specifically to FIG. 6, process 600 is shown to include slaveactuator 104 sending a detection signal to master actuator 102 viabidirectional communications link 228 (step 602). Slave actuator 104 cangenerate the detection signal according to stored criteria and canoutput the detection signal via input data connection 110. Masteractuator 102 can monitor feedback data connection 114 for the detectionsignal. Master actuator 102 can identify the detection signal bycomparing the signals received at feedback data connection 114 with astored representation of the detection signal.

In response to receiving the detection signal at feedback dataconnection 114, master actuator 102 can set its operating mode to amaster operating mode (step 604) and can send a reply signal back toslave actuator 104 via bidirectional communications link 228 (step 606).Master actuator 102 can generate the reply signal according to storedcriteria and can output the reply signal via feedback data connection114.

Slave actuator 104 can monitor input data connection 110 for the replysignal. Slave actuator 104 can identify the reply signal by comparingthe signals received at input data connection 110 with a storedrepresentation of the reply signal. In response to receiving the replysignal at input data connection 110, slave actuator 104 can set itsoperating mode to a slave operating mode (step 608).

Referring now to FIG. 7A, a block diagram illustrating master actuator102 and slave actuator 104 in greater detail is shown, according to someembodiments. Actuators 102 and 104 can be identical or substantiallyidentical and can include the same or similar components. For example,each of actuators 102 and 104 is shown to include an input connection736, a feedback connection 734, a slave handshake circuit 702, aproportional input and master detection circuit 710, a microcontroller716, a slave detection circuit 718, and a feedback output circuit 724.

The input connection 736 of master actuator 102 can be connected withoutput data connection 120 of controller 100. Feedback connection 734 ofmaster actuator 102 can be connected via a bidirectional communicationslink 732 with input connection 736 of slave actuator 104. Feedbackconnection 734 of slave actuator 104 can be connected with inputconnection 122 of controller 100.

Proportional input and master detection circuit 710 can be configured toperform the functions of proportional input module 154 and master signaldetector 142, as described with reference to FIG. 4. For example,proportional input and master detection circuit 710 is shown to includea division module 712, a low pass filter 714, and a voltage comparator708. Division module 712 can apply a division factor to the input signalreceived at input connection 736. Division module 712 can provide thedivided signal to low pass filter 714. Low pass filter 714 can filterthe divided signal from division module 712 and can provide the filteredsignal as an analog input 742 to voltage comparator 708 andmicrocontroller 716. Voltage comparator 708 can be configured to monitorthe output of low pass filter 714 for the master detection signal. Themaster detection signal can be received from a master actuator if inputconnection 736 is connected with the feedback connection of anotheractuator. Voltage comparator 708 can provide an analog or digital input740 to microcontroller 716 indicating whether the master detectionsignal is received at input connection 736.

Microcontroller 716 can be configured to generate the master detectionsignal and to provide the master detection signal as an output viafeedback connection 734. In some embodiments, microcontroller 716generates the master detection signal according to a signal protocol. Insome embodiments, the master detection signal is a series of voltagepulses. Microcontroller 716 can output the master detection signal viaPWM/DO output 744. PWM/DO output 744 can communicate the masterdetection signal to feedback connection 734 via feedback output circuit724.

Feedback output circuit 724 is shown to include a low pass filter 726, again stage 728, and a buffer stage 730. Low pass filter 726 can filterthe output signal from PWM/DO output 744 of microcontroller 716. Gainstage 728 can multiply the filtered signal from low pass filter 726 by amultiplication factor and provide the multiplied signal to buffer stage730. Buffer stage 730 can output the signal from gain stage 728 as afeedback signal via feedback connection 734.

Still referring to FIG. 7A, microcontroller 716 can be configured toreceive an analog or digital input 740 indicating whether the masterdetection signal has been received at input connection 736. If input 740indicates that the master detection signal has been received,microcontroller 716 can generate a reply signal and provide the replysignal as an analog or digital output 746 to input connection 736. Inother embodiments, microcontroller 716 causes slave handshake circuit702 to generate the reply signal. For example, microcontroller 716 canprovide a command to slave acknowledge circuit 704 via output 746 andslave acknowledge circuit 704 can generate the reply signal in responseto receiving the command from microcontroller 716. If input 740indicates that the master detection signal has been received,microcontroller 716 can instruct slave acknowledge circuit 704 togenerate the reply signal. The reply signal can be communicated throughbidirectional communications link 732 to the other controller (i.e.,back to the master controller).

Microcontroller 716 can be configured to set an operating mode for thecorresponding actuator. For example, if digital input 740 indicates thatthe master detection signal has been received, microcontroller 716 canset the corresponding actuator to operate in the slave operating mode.Microcontroller 716 can be configured to receive analog input 748 and todetermine whether analog input 748 matches the reply signal. If analoginput 748 matches the reply signal, microcontroller 716 can set thecorresponding actuator to operate in the master operating mode. Ifmicrocontroller 716 does not observe either the master detection signalor the reply signal as an input, microcontroller 716 can set thecorresponding actuator to operate in a normal (i.e., non-linked)operating mode.

Slave detection circuit 718 can be configured to perform the functionsof reply signal detector 148, as described with reference to FIG. 4. Forexample, slave detection circuit 718 can monitor feedback connection 734for the reply signal received via the bidirectional communications link732. Slave detection circuit 718 is shown to include a voltagecomparator 722 and a low pass filter 720. Voltage comparator 722 candetermine whether the signal received via bidirectional communicationslink 732 matches the reply signal and can provide a reply detectionsignal to low pass filter 720 when the reply signal is detected. Lowpass filter 720 can filter the reply detection signal from voltagecomparator 722 and can provide the filtered signal as an analog input748 to microcontroller 716.

Referring now to FIG. 7B, a circuit diagram illustrating selectedportions of master actuator 102 and slave actuator 104 in greater detailis shown, according to some embodiments. Master actuator 102 is shown toinclude a feedback output circuit 724. Feedback output circuit 724 caninclude a voltage source V₁ configured to generate a voltage signalV_(signal) at wire 752. V_(signal) can be a series of digital pulseswithin a predetermined voltage range (e.g., 0-10 VDC). For example,V_(signal) can include a series of three 1 Hz pulses from 0-10 VDCfollowed by a 10 VDC signal. In some embodiments, V_(signal) is a pulsewidth modulated signal. For example, feedback output circuit 724 cangenerate V_(signal) by applying a 100% duty cycle and a 0% duty cycle tothe voltage source V₁.

Feedback output circuit 724 can transform V_(signal) into a feedbackvoltage signal V_(fb) and output the feedback voltage signal V_(fb) atfeedback connection 734. Feedback output circuit 724 is shown to includea non-inverting amplifier consisting of op amp U₃, resistor R₁₁, andresistor R₁₂. Op amp U₃ receives an input voltage V_(in,3) at itsnon-inverting input and produces an output voltage V_(out,3) at itsoutput terminal. In some embodiments, the input voltage V_(in,3) isV_(signal) or a fraction of V_(signal). In some embodiments, the outputvoltage V_(out,3) is defined by the formula

$V_{{out},3} = {{V_{{in},3}\left( {1 + \frac{R_{11}}{R_{12}}} \right)}.}$The output voltage V_(out,3) is provided as an input to the positiveterminal of op amp U₇. Op amp U₇ is arranged in a voltage followerconfiguration such that the output voltage V_(out,7) of op amp U₇ is thesame as the input voltage V_(out,3). In some embodiments, capacitor C₆causes feedback output circuit 724 to store energy such that V_(fb)asymptotically increases to the value of V_(signal) when a 100% dutycycle is applied (e.g., when V_(signal) is 10 VDC) and asymptoticallydecreases to zero when a 0% duty cycle is applied (e.g., when V_(signal)is VDC).

Feedback connection 734 of master actuator 102 can be connected viabidirectional communications link 732 with input connection 736 of slaveactuator 104. Slave actuator 104 can receive the feedback voltage signalV_(fb) at input connection 736. Slave actuator 104 can pass the feedbackvoltage signal V_(fb) through a series of resistors R₇, R₄, R₁, and R₂and an op amp U₁. In some embodiments, resistors R₇, R₄, R₁, and R₂function as voltage dividers such that the input voltage V_(in,1) to opamp U₁ is a fraction of the feedback voltage signal V_(fb). Op amp U₁ isarranged in a voltage follower configuration such that the outputvoltage V_(out,1) of op amp U₁ is the same as the input voltageV_(in,1).

Slave actuator 104 is shown to include a master detection circuit 710.Master detection circuit 710 receives the output signal V_(out,1) fromop amp U₁. Master detection circuit 710 is shown to include a resistorR₉, a resistor R₁₉, and an op amp U₅. These components of masterdetection circuit 710 form a comparator with hysteresis (i.e., anon-inverting Schmitt trigger). In this configuration, the input voltageV_(out,1) is applied through the resistor R₉ to the non-inverting inputof op amp U₅ and a reference voltage V_(ref) is applied to the invertinginput of op amp U₅. The output voltage V_(out,5) of op amp U₅ willswitch to a high voltage V_(high) (e.g., 5 VDC) when the input voltageV_(out,1) exceeds a high switching threshold V_(thresh,high) and willswitch to a low voltage V_(low) (e.g., 0 VDC) when the input voltageV_(out,1) drops below a low switching threshold V_(thresh,low). In someembodiments, the high switching threshold V_(thresh,high) is defined bythe equation

$V_{{thresh},{high}} = {V_{ref} + {\frac{R_{9}}{R_{19}}V_{sat}}}$and the low switching threshold V_(thresh,low) is defined by theequation

${V_{{thresh},{high}} = {V_{ref} - {\frac{R_{9}}{R_{19}}V_{sat}}}},$where V_(sat) is the maximum output voltage (e.g., 15 VDC).

The output voltage V_(out,5) of op amp U₅ can be provided tomicrocontroller 716 as the master detection signal V_(master_detect).The master detection signal V_(master_detect) will switch to the lowvoltage V_(low) shortly after the 0% duty cycle is applied to V_(signal)and will switch to the high voltage V_(high) shortly after the 100% dutycycle is applied to V_(signal). Accordingly, the master detection signalV_(master_detect) can experience a series of digital pulses that aretriggered by the series of pulses in V_(signal.)

Microcontroller 716 can analyze the master detection signalV_(master_detect) to determine whether master detection signalV_(master_detect) matches a stored master detection signal. For example,microcontroller 716 can monitor the master detection signalV_(master_detect) for a series of digital pulses. In response to adetermination that the master detection signal V_(master_detect) matchesthe stored master detection signal, microcontroller 716 can set theoperating mode of slave actuator 104 to a slave operating mode.

Slave actuator 104 is shown to include a reply signal circuit 750. Replysignal circuit 750 can receive a reply signal V_(slv_ack) (e.g., 5 VDC)from microcontroller 716 in response to microcontroller 716 determiningthat the master detection signal V_(master_detect) matches the storedmaster detection signal. The reply signal V_(slv_ack) can be providedthrough resistor R₂₂ to the gate of transistor M₁, which can beimplemented as a NMOS transistor. When the reply signal V_(slv_ack) isprovided to transistor M₁, current can flow from input connection 736,through diode D₅ and transistor M₁ (downward in FIG. 7B), to ground. Thecurrent flow through transistor M₁ causes the feedback voltage V_(fb) todrop below a threshold voltage (e.g., 1 VDC) for the duration that thereply signal reply signal V_(slv_ack) is applied (e.g., 0.5 seconds).

Master actuator 102 is shown to include a slave detection circuit 718.Slave detection circuit can receive the feedback signal V_(fb) fromfeedback connection 734 via resistor R₁₀. Slave detection circuit 718 isshown to include a resistor R₂₇, a resistor R₂₆, and an op amp U₄. Thesecomponents of slave detection circuit 718 form a comparator withhysteresis (i.e., a non-inverting Schmitt trigger). In thisconfiguration, the feedback signal V_(fb) is applied through theresistor R₂₇ to the non-inverting input of op amp U₄ and a referencevoltage V_(ref)(e.g., 0-5 VDC) is applied to the inverting input of opamp U₄. The output voltage V_(out,4) of op amp U₄ will switch to a highvoltage V_(high) (e.g., 5 VDC) when the feedback signal V_(fb) exceeds ahigh switching threshold V_(thresh,high) and will switch to a lowvoltage V_(low) (e.g., 0 VDC) when the feedback signal V_(fb) dropsbelow a low switching threshold V_(thresh,low). In some embodiments, thehigh switching threshold V_(thresh,high) is defined by the equation

$V_{{thresh},{high}} = {V_{ref} + {\frac{R_{27}}{R_{26}}V_{sat}}}$and the low switching threshold V_(thresh,low) is defined by theequation

${V_{{thresh},{high}} = {V_{ref} - {\frac{R_{27}}{R_{26}}V_{sat}}}},$where V_(sat) is the maximum output voltage (e.g., 15 VDC).

The output voltage V_(out,4) of op amp U₄ can be provided tomicrocontroller 716 as the slave detection signal V_(slv_detect). Theslave detection signal V_(slv_detect) will switch to the low voltageV_(low) when the reply signal V_(slv_ack) is provided to transistor M₁.Accordingly, the slave detection signal V_(slv_detect) can drop to avalue of 0 VDC for the duration that the reply signal V_(slv_ack) isprovided by reply circuit 750 (e.g., 0.5 seconds).

Microcontroller 716 can analyze the slave detection signalV_(slv_detect) to determine whether the slave detection signalV_(slv_detect) matches a stored slave detection signal. In response to adetermination that the slave detection signal V_(slv_detect) matches thestored slave detection signal, microcontroller 716 can set the operatingmode of master actuator 102 to a master operating mode.

Referring now to FIG. 8, a flowchart of a process 800 for automaticallyselecting an operating mode for a HVAC actuator is shown, according tosome embodiments. Process 800 can be performed by any actuator in a HVACsystem (e.g., damper actuators 54-58, valve actuators 88-90, fanactuators, pump actuators, etc.). In some embodiments, process 800 isperformed by a processing circuit of a HVAC actuator. For example,process 800 can be performed by processing circuit 134 or bymicrocontroller 716 of one or more of actuators 102-106, as describedwith reference to FIGS. 4-7.

Process 800 is shown to include transmitting a first data signal via abidirectional communications link between a first actuator and a secondactuator (step 802). The first data signal can be a master-slavedetection signal or a reply signal. If the first data signal is amaster-slave detection signal, the first data signal can be transmittedupon the actuator receiving power. If the first data signal is a replysignal, the first data signal can be transmitted in response toreceiving the master-slave detection signal from another actuator via abidirectional communications link.

Process 800 is shown to include monitoring the bidirectionalcommunications link for a second data signal (step 804). The second datasignal can be a reply signal or a master-slave detection signal. If thefirst data signal is a master-slave detection signal, the second datasignal can be the reply signal. If the first data signal is a replysignal, the second data signal can be the master-slave detection signal.

In various embodiments, the order of steps 802 and steps 804 can bereversed. For example, if the first data signal is the master-slavedetection signal and the second data signal is the reply signal, step802 can be performed before step 804. However, if the first data signalis the reply signal and the second data signal is the master-slavedetection signal, step 802 can be performed before after 804.

Process 800 is shown to include selecting an operating mode for at leastone of the first actuator and the second actuator based on whether thesecond data signal is received via the bidirectional communications link(step 806). If the second data signal is the master-slave detectionsignal, step 806 can include selecting the slave operating mode for theactuator. If the second data signal is the reply signal, step 806 caninclude selecting the master operating mode for the actuator. If neitherthe master-slave detection signal nor the reply signal are received viathe bi-directional communications link, step 806 can include selectingthe non-linked (e.g., normal) operating mode for the actuator.

Referring now to FIG. 9, a flowchart of a process 900 for automaticallyselecting an operating mode for a HVAC actuator is shown, according tosome embodiments. Process 900 can be performed by any actuator in a HVACsystem (e.g., damper actuators 54-58, valve actuators 88-90, fanactuators, pump actuators, etc.). In some embodiments, process 900 isperformed by a processing circuit of a HVAC actuator. For example,process 900 can be performed by processing circuit 134 or bymicrocontroller 716 of one of actuators 102-106, as described withreference to FIGS. 3-7.

Process 900 is shown to include transmitting a master-slave detectionsignal via a feedback data connection of an actuator (step 902). If theactuator is arranged as a master actuator, the feedback data connectioncan be connected with an input data connection of another actuator. Theconnection between actuators can be a bidirectional communications link.However, if the actuator is arranged as a slave actuator or in anon-linked arrangement, the feedback data connection may not beconnected with the input data connection of another actuator.

Process 900 is shown to include monitoring an input data connection ofthe actuator for the master-slave detection signal (step 904). If theactuator is arranged as a slave actuator, the input data connection canbe connected with a feedback data connection of another actuator. If theother actuator also transmits the master-slave detection signal via itsfeedback data connection, the master-slave detection signal will bereceived at the input data connection in step 904. However, if theactuator is arranged as a master actuator or in a non-linkedarrangement, the input data connection may not be connected with thefeedback connection of another actuator and the master-slave detectionsignal will not be received in step 904.

Process 900 is shown to include transmitting a reply signal via theinput data connection in response to detecting the master-slavedetection signal at the input data connection (step 906). Step 906 is anoptional step that can be performed if the master-slave detection signalis detected in step 904. The master-slave detection signal can bedetected in step 904 if the actuator is arranged as a slave actuator. Ifthe actuator is not arranged as a slave actuator, the master-slavedetection signal may not be received in step 904 and step 906 may not beperformed.

Process 900 is shown to include monitoring the feedback data connectionfor the reply signal (step 908). If the actuator is arranged as a masteractuator, the feedback data connection can be connected with an inputdata connection of another actuator. If the other actuator also performsprocess 900, the reply signal can be received in step 908. However, ifthe actuator is arranged as a slave actuator or in a non-linkedarrangement, the feedback data connection may not be connected with theinput data connection of another actuator and the reply signal will notbe received in step 908.

Process 900 is shown to include selecting an operating mode for theactuator based on whether the master-slave detection signal or the replysignal is detected by the monitoring (step 910). If the monitoring instep 904 detects the master-slave detection signal, step 910 can includesetting the operating mode for the actuator to a slave operating mode.If the monitoring in step 908 detects the reply signal, step 910 caninclude setting the operating mode for the actuator to a masteroperating mode. If neither of the monitoring steps detect themaster-slave detection signal or the reply signal, step 910 can includesetting the operating mode for the actuator to a non-linked (e.g.,normal) operating mode.

Referring now to FIG. 10, a flowchart of a process 1000 forautomatically selecting an operating mode for a HVAC actuator is shown,according to some embodiments. Process 1000 can be performed by anyactuator in a HVAC system (e.g., damper actuators 54-58, valve actuators88-90, fan actuators, pump actuators, etc.). In some embodiments,process 1000 is performed by a processing circuit of a HVAC actuator.For example, process 1000 can be performed by processing circuit 134 orby microcontroller 716 of one of actuators 102-106, as described withreference to FIGS. 3-7.

Process 1000 is shown to include transmitting a master signal via afeedback data connection of an actuator (step 1002). If the actuator isarranged as a master actuator, the feedback data connection can beconnected with an input data connection of another actuator. Theconnection between actuators can be a bidirectional communications link.However, if the actuator is arranged as a slave actuator or in anon-linked arrangement, the feedback data connection may not beconnected with the input data connection of another actuator.

Process 1000 is shown to include monitoring an input data connection ofthe actuator for the master signal (step 1004). If the actuator isarranged as a slave actuator, the input data connection can be connectedwith a feedback data connection of another actuator. If the otheractuator also transmits the master signal via its feedback dataconnection, the master signal will be received at the input dataconnection in step 1004. However, if the actuator is arranged as amaster actuator or in a non-linked arrangement, the input dataconnection may not be connected with the feedback connection of anotheractuator and the master signal will not be received in step 1004.

Process 1000 is shown to include determining whether the master signalis detected at the input data connection (step 1006). If the mastersignal is detected at the input data connection of the actuator in step1004 (i.e., the result of step 1006 is “yes”), process 1000 can proceedto transmitting a reply signal via the input data connection (step 1008)and selecting a slave operating mode for the actuator (step 1010).

If the master signal is not detected at the input data connection of theactuator in step 1004 (i.e., the result of step 1006 is “no”), process1000 can proceed to monitoring the feedback data connection for thereply signal (step 1012). If the actuator is arranged as a masteractuator, the feedback data connection can be connected with an inputdata connection of another actuator. If the other actuator also performsprocess 1000, the reply signal can be received in step 1012. However, ifthe actuator is arranged as a slave actuator or in a non-linkedarrangement, the feedback data connection may not be connected with theinput data connection of another actuator and the reply signal will notbe received in step 1012.

Process 1000 is shown to include determining whether the reply signal isdetected at the feedback data connection (step 1014). If the replysignal is detected at the feedback data connection of the actuator instep 1012 (i.e., the result of step 1014 is “yes”), process 1000 canproceed to selecting a master operating mode for the actuator (step1016). If the reply signal is not detected at the feedback dataconnection of the actuator in step 1012 (i.e., the result of step 1014is “no”), process 1000 can proceed to selecting a non-linked operatingmode for the actuator (step 1018).

Wireless Configuration and Communication

Referring now to FIG. 11, a block diagram of an actuator 1100 is shown,according to some embodiments. Actuator 1100 can be configured towirelessly communicate with an external device (e.g., mobile device1140, a controller, another actuator, etc.) to send and receive varioustypes of data related to the operation of actuator 1100 (e.g., firmwaredata, control logic, model identification parameters, configurationparameters, diagnostic data, etc.). Advantageously, actuator 1100 cancommunicate with the external device without requiring any wired poweror data connections to actuator 1100. This allows actuator 1100 to sendand receive data in the event that physical access to actuator 1100 islimited. For example, actuator 1100 can be installed in a location thatis not readily accessible by a user or service technician.

In some embodiments, actuator 1100 can communicate with external deviceswhile actuator 1100 is still in its packaging at a manufacturer facilityor a distributor location. Actuator 1100 can be constructed and packagedas a generic actuator and subsequently configured with suitablefirmware, software, configuration parameters, or other data specific toa particular actuator model and/or implementation. Operational data suchas end of line test data or other diagnostic data can be extracted fromactuator 1100 without requiring a physical data connection.

Still referring to FIG. 11, actuator 1100 is shown to include atransducer 1102, a processing circuit 1104, a power circuit 1110, and awireless transceiver 1112. Transducer 1102 can be any apparatus capableof providing forces and/or motion in response to a control signal. Forexample, transducer 1102 can be any of a variety of mechanicaltransducers such as rotary motors, linear motors, hydraulic or pneumaticpistons/motors, piezoelectric elements, relays, comb drives, thermalbimorphs, or other similar devices to provide mechanical motion.Transducer 1102 can provide any combination of linear, curved, or rotaryforces/motion.

In some embodiments, transducer 1102 is connected with one or moremechanical components (e.g., gears, pulleys, cams, screws, levers,crankshafts, ratchets, etc.) capable of changing or affecting the motionprovided by transducer 1102. In some embodiments, transducer 1102 maynot produce significant motion in operation. For example, transducer1102 can be operated to exert a force or torque to an external element(e.g., a holding force) without affecting significant linear or rotarymotion.

Processing circuit 1104 can be configured to operate transducer 1102.Processing circuit 1104 is shown to include a processor 1106 and memory1108. Processor 1106 can be a general purpose or specific purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a group of processingcomponents, or other suitable processing components. Processor 1106 canbe configured to execute computer code or instructions stored in memory1108 or received from other computer readable media (e.g., CDROM,network storage, a remote server, etc.).

Memory 1108 can include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 1108 can include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory1108 can include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 1108 can be communicably connected toprocessor 1106 via processing circuit 1104 and can include computer codefor executing (e.g., by processor 1106) one or more processes describedherein.

Memory 1108 can store various types of data related to the operation ofactuator 1100. For example, memory 1108 is shown to include firmware1120, control logic 1122, and configuration parameters 1128. In someembodiments, control logic 1122 is a component of firmware 1120. Controllogic 1122 can include one or more control programs that are used byprocessing circuit 1104 to operate transducer 1102. The control programcan include logic for operating transducer 1102 based on variableconfiguration parameters (e.g., configuration parameters 1128) that areseparate from the control program. Configuration parameters 1128 caninclude, for example, operational parameters such as actuation span(e.g., linear distance, degrees of rotation, etc.), offset, actuationspeed, timing, or other parameters that configure actuator 1100 for aspecific implementation.

Memory 1108 is shown to include model identification parameters 1126. Insome embodiments, processing circuit 1104 is capable of operatingmultiple different actuator models. Model identification parameters 1126can identify a particular actuator model and/or define configurationsettings for a specific actuator model. Processing circuit 1104 can usemodel identification parameters 1126 to operate transducer 1102according to configuration settings and/or control logic specific to theactuator model identified by model identification parameters 1126.

Memory 1108 is shown to include hyperlinks 1124. Hyperlinks 1124 can belinks to a product information webpage, a product catalog, a productmanual, an installation manual, an order form, or any other resourcerelated to actuator 1100. In some embodiments, hyperlinks 1124 arespecific to a particular actuator model defined by model identificationparameters 1126. Hyperlinks 1124 can be communicated to a client device(e.g., mobile device 1140) via wireless transceiver 1112 and used by theclient device to locate various resources associated with actuator 1100.

Memory 1108 is shown to include a diagnostics module 1132, diagnosticsresults 1134, and log data 1136. Diagnostics module 1132 can beconfigured to perform a diagnostic test of actuator 1100. Diagnostictests can include, for example, a span or range test, a force/torquetest, a calibration test, a failure modes test, a timing/speed test, orany other type of diagnostic test that can be performed by actuator1100. Results of the diagnostic tests can be stored in memory 1108 asdiagnostics results 1134. Diagnostics results 1134 can be communicatedto an external system or device (e.g., a system controller, a fieldcontroller, an economizer controller, a client device, a factory orlaboratory diagnostics system, etc.) via wireless transceiver 1112.

Log data 1136 can include any information related to the operation ofactuator 1100. For example, log data 1136 can include actuatorpositions, control signal values, feedback signal values, an amount offorce or torque exerted by actuator 1100, a measured temperature, or anyother variable generated or used by actuator 1100. Log data 1136 canstore information with time stamps indicating a time at which the storedvalues were used or observed by actuator 1100. Log data 1136 can becommunicated to an external system or device to evaluate actuatorperformance and/or to perform external diagnostics.

Memory 1108 is shown to include a master/slave detection module 1130.Master-slave detection module 1130 can include the functionality offeedback generator 140, master signal detector 142, reply signalgenerator 146, reply signal detector 148, and operating mode selector144, as described with reference to FIG. 4. For example, master-slavedetection module 1130 can be configured to use a master-slave detectionsignal communicated via wireless transceiver 1112 and/or wiredcommunications interface 1114 to select an operating mode for actuator1100. The operating modes can include a master operating mode, a slaveoperating mode, and a non-linked operating mode. Processing circuit 1104can be configured to operate transducer 1102 in response to a controlsignal received wireless transceiver 1112 and/or wired communicationsinterface 1114 according to the selected operating mode.

Still referring to FIG. 11, actuator 1100 is shown to include a powercircuit 1110. Power circuit 1110 can be configured to draw power from awireless signal (e.g., an alternating magnetic or electric field)received via wireless transceiver 1112. For example, wirelesstransceiver 1112 can include an antenna coil that is exposed to amagnetic or electric field. The field can be produced by mobile device1140 or another external device. In some embodiments, the magnetic orelectric field is a NFC field (i.e., an alternating magnetic field witha frequency of approximately 13.56 MHz, compatible with near fieldcommunications (NFC) devices). The magnetic field can induce a voltagein power circuit 1110. In some embodiments, power circuit 1110 storesenergy derived from the wireless signal using one or more capacitors.

Advantageously, power circuit 1110 can be configured to power processingcircuit 1104 and wireless transceiver 1112 using the power drawn fromthe wireless signal received at wireless transceiver 1112. Thisadvantage allows actuator 1100 to engage in bidirectional communicationswith an external device regardless of whether actuator 1100 receivespower from a wired power connection. For example, actuator 1100 cancommunicate with external devices while actuator 1100 is still in itspackaging at a manufacturer facility or a distributor location. Actuator1100 can be constructed and packaged as a generic actuator andsubsequently configured with suitable firmware, software, configurationparameters, or other data specific to a particular actuator model and/orimplementation.

Still referring to FIG. 11, actuator 1100 is shown to include a wirelesstransceiver 1112. Wireless transceiver 1112 can be configured tofacilitate bidirectional wireless data communications between processingcircuit 1104 and an external device (e.g., mobile device 1140). Wirelesstransceiver can be used by processing circuit 1104 to transmit datastored in memory 1108 to the external device and/or to wirelesslyreceive data from the external device. In some embodiments, the externaldevice includes a user interface 1142 that can be used to view the datacommunicated via wireless transceiver 1112.

Data communicated via wireless transceiver 1112 can include firmwaredata 1120, control logic data 1122, hyperlinks 1124, modelidentification parameters 1126, configuration parameters 1128,master-slave detection logic or signals, diagnostics logic or results1134, log data 1136, device identifiers (e.g., serial numbers, MACaddresses, etc.), or any other type of information used by actuator 1100and/or stored in memory 1108. Processing circuit 1104 can retrieve datafrom memory 1108 and transmit the retrieved data to the external devicevia wireless transceiver 1112. Processing circuit 1104 can receive datafrom the external device via wireless transceiver 1112 and store thereceived data in memory 1108.

Wireless transceiver 1112 can utilize any of a variety of wirelesstechnologies and/or communications protocols for wireless datacommunications. For example, wireless transceiver 1112 can use nearfield communications (NFC), Bluetooth, Bluetooth low energy (BLE), WiFi,WiFi direct, radio frequency communication (e.g., RFID, radio waves,etc.), optical communication, electromagnetic signals, soundtransmission, or any other wireless communications technology.

Wireless transceiver 1112 can be configured to operate in a powered modeor a non-powered mode. In the powered mode, wireless transceiver 1112can receive power from another energy source (e.g., a wired powerconnection, a battery, etc.). In the non-powered mode, wirelesstransceiver 1112 can draw power from an electromagnetic field, wave, orradiation using an antenna or receptor. Wireless transceiver 1112 canuse any of a variety of wireless energy transfer technologies (e.g.,electrodynamic induction, electrostatic induction, lasers, microwaves,etc.) to obtain or harvest energy wirelessly. Advantageously, wirelesstransceiver 1112 allows actuator 1100 to engage in bidirectionalwireless data communications without requiring a wired power or dataconnection to an external device.

Still referring to FIG. 11, actuator 1100 is shown to include a wiredcommunications interface 1114. In some embodiments, actuator 1100 useswired communications interface 1114 to communicate with a controller(e.g., controller 100, described with reference to FIGS. 2-6), anotheractuator, or to an external system or device. In other embodiments,actuator 1100 uses wireless transceiver 1112 for such communications.

Wired communications interface 1114 is shown to include an input dataconnection 1116 and a feedback data connection 1118. If actuator 1100 isarranged as a master actuator, input data connection 1116 can beconnected to the output of a controller and feedback data connection1118 can be connected to the input connection of another actuator. Ifactuator 1100 is arranged as a slave actuator, input data connection1116 can be connected to the feedback data connection of anotheractuator and feedback data connection 1118 can be connected to the inputof the controller or may not be connected to anything. Wiredcommunications interface 1114 can allow actuator 1100 to function as anyof actuators 54-58, 88-90, or 102-106, as described with reference toFIGS. 2-6.

Referring now to FIG. 12, a flowchart of a process for wirelesslyconfiguring and communicating with an actuator in a HVAC system isshown, according to some embodiments. In some embodiments, process 1200is performed by actuator 1100, as described with reference to FIG. 11.

Process 1200 is shown to include drawing power from a wireless signalreceived at a wireless transceiver of an actuator (step 1202). Step 1202can include drawing power from an electromagnetic field, wave, orradiation using an antenna or receptor. Step 1202 can include using anyof a variety of wireless energy transfer technologies (e.g.,electrodynamic induction, electrostatic induction, lasers, microwaves,etc.) to obtain or harvest energy wirelessly.

Process 1200 is shown to include using the power drawn from the wirelesssignal to power a processing circuit of the actuator (step 1204). Thepower drawn from the wireless signal can be stored in one or morecapacitors within the actuator and can be used to power the processingcircuit and/or the wireless transceiver. Advantageously, this allows theactuator to engage in bidirectional wireless data communications withoutrequiring a wired power or data connection to an external device.

Process 1200 is shown to include transmitting data stored in a memory ofthe actuator to an external device via the wireless transceiver (step1206) and receiving data from the external device via the wirelesstransceiver (step 1208). In some embodiments, process 1200 can includeonly one of steps 1206 and step 1208. For example, the actuator cantransmit data stored in the memory of the actuator to the externaldevice without receiving data from the external device. Alternatively,the actuator can receive data from the external device withouttransmitting data stored in the memory of the actuator. One or both ofsteps 1206 and 1208 can be performed in various implementations.

Data communicated via the wireless transceiver can include firmware data1120, control logic data 1122, hyperlinks 1124, model identificationparameters 1126, configuration parameters 1128, master-slave detectionlogic or signals, diagnostics logic or results 1134, log data 1136,device identifiers (e.g., serial numbers, MAC addresses, etc.), or anyother type of information used by the actuator and/or stored in thememory of the actuator.

Process 1200 is shown to include storing the data received from theexternal device in the memory of the actuator (step 1210). Step 1210 canbe performed in response to receiving data from the external device viathe wireless transceiver. The data received from the wirelesstransceiver can replace existing data stored in the memory of theactuator or can be stored in free space within the memory of theactuator. For example, the actuator can be constructed and packaged as ageneric actuator (e.g., without firmware data, control logic, and/orconfiguration parameters) and subsequently configured with suitablefirmware, software, configuration parameters, or other data specific toa particular actuator model and/or implementation.

Near Field Communication and Configuration

Referring now to FIG. 13, a block diagram of a building device 1300 isshown, according to some embodiments. Building device 1300 can beconfigured to wirelessly communicate with a nearby external device(e.g., mobile device 1340, etc.) to send and receive various types ofdata related to the operation of building device 1300 (e.g., firmwaredata, control logic, model identification parameters, configurationparameters, diagnostic data, etc.) using near field communicationprotocol. Advantageously, building device 1300 can communicate with theexternal device without requiring any wired power or data connections tobuilding device 1300. This allows a user or service technician to senddata to and receive data from building device 1300 using an externaldevice brought into close proximity with building device 1300.

Building device 1300 can be any device utilized in a building automationsystem. For example, it is contemplated that building device can be anactuator (e.g., rotary actuator, linear actuator, etc.), a sensor (e.g.,temperature sensor, pressure sensor, vibration sensor, humidity sensor,flow sensor, etc.), valves, controllers, and other types of devices thatcan be used for monitoring or controlling an automated system orprocess.

Data received from building device 1300 can include, for example,collected sensor data, diagnostic data, addresses, and alerts (e.g.,fault conditions). Data sent to building device 1300 can include, forexample, network addressing data, setpoint adjustments, modelconfiguration (e.g., torque, travel time, model, transducer calibration,etc.), field parameters (e.g., DA/RA, span, offset, flow limitation,etc.), and firmware downloads. Near field communication between buildingdevice 1300 and the external device allows data to be retrieved from andwritten to building device 1300 without physically interacting withbuilding device 1300, such as partially disassembling building device1300 by removing an outer housing to access dip switches or otherinternal components. Near field communication between building device1300 and the external device allows for a building device to be quicklyand easily replaced with a replacement building device. For example, thecurrent configuration of the building device being removed can be readby the external device, stored, and written to the replacement buildingdevice.

Still referring to FIG. 13, building device 1300 is shown to include aprocessing circuit 1302 and an NFC circuit 1310. Processing circuit 1302is shown to include a processor 1306 and memory 1308. In someembodiments, building device 1300 can include a transducer 1304. Forexample, if building device 1300 is embodied as an actuator, transducer1304 can be any apparatus capable of providing forces and/or motion inresponse to a control signal. Transducer 1304 can be any of a variety ofmechanical transducers such as rotary motors, linear motors, hydraulicor pneumatic pistons/motors, piezoelectric elements, relays, combdrives, thermal bimorphs, or other similar devices to provide mechanicalmotion. Transducer 1304 can provide any combination of linear, curved,or rotary forces/motion. If building device 1300 is embodied as asensor, transducer 1304 can be any apparatus capable of providing anelectrical signal in response to a mechanical force or change in acharacteristic of the environment. Transducer 1304 can be any of avariety of sensors, such as temperature sensors, pressure sensors,vibration sensors, flow sensors, humidity sensors, smoke detectors,occupancy sensors, CO₂ sensors, or other various types of sensors.

Building device 1300 can be configured to in include multipletransducers. That is, a single building device 1300 can be able to bereconfigured to operate in different ways in a building system. Asdescribed in more detail below, building device 1300 can be programmedto utilize different transducers.

In some embodiments, transducer 1304 is connected with one or moremechanical components (e.g., gears, pulleys, cams, screws, levers,crankshafts, ratchets, etc.) capable of changing or affecting the motionprovided by transducer 1304 or provided to transducer 1304. In someembodiments, transducer 1304 may not produce significant motion inoperation. For example, transducer 1304 can be operated to exert a forceor torque to an external element (e.g., a holding force) withoutaffecting significant linear or rotary motion.

Processor 1306 can be a general purpose or specific purpose processor,an application specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a group of processing components, orother suitable processing components. Processor 1306 can be configuredto execute computer code or instructions stored in memory 1308 orreceived from other computer readable media (e.g., CDROM, networkstorage, a remote server, etc.). Processing circuit 1302 can beconfigured to operate transducer 1304. Processing circuit 1302 can beconfigured to receive signals from transducer 1304.

Memory 1308 can include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 1308 can include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory1308 can include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 1308 can be communicably connected toprocessor 1306 via processing circuit 1302 and can include computer codefor executing (e.g., by processor 1306) one or more processes describedherein.

Memory 1308 can store various types of data related to the operation ofbuilding device 1300. For example, memory 1308 is shown to includefirmware 1320, control logic 1322, and configuration parameters 1328. Insome embodiments, control logic 1322 is a component of firmware 1320.Control logic 1322 can include one or more control programs that areused by processing circuit 1302 to operate transducer 1304 or to processelectrical signals received from transducer 1304. The control programcan include logic for operating transducer 1304 or utilizing electricalsignals provided by transducer 1304 based on variable configurationparameters (e.g., configuration parameters 1328) that are separate fromthe control program. Configuration parameters 1328 can include, forexample, operational parameters such as actuation span (e.g., lineardistance, degrees of rotation, etc.), offset, actuation speed, timing,setpoints, or other parameters that configure building device 1300 for aspecific implementation.

Memory 1308 is shown to include model identification parameters 1326. Insome embodiments, processing circuit 1302 is capable of operatingmultiple different building device models. Model identificationparameters 1326 can identify a particular building device model and/ordefine configuration settings for a specific building device model.Processing circuit 1302 can use model identification parameters 1326 tooperate transducer 1304 or utilize electrical signals provided bytransducer 1304 according to configuration settings and/or control logicspecific to the building device model identified by model identificationparameters 1326.

Memory 1308 is shown to include hyperlinks 1324. Hyperlinks 1324 can belinks to a product information webpage, a product catalog, a productmanual, an installation manual, an order form, or any other resourcerelated to building device 1300. In some embodiments, hyperlinks 1324are specific to a particular building device model defined by modelidentification parameters 1326. Hyperlinks 1324 can be communicated to aclient device (e.g., mobile device 1340) via NFC circuit 1310 and usedby the client device to locate various resources associated withbuilding device 1300.

Memory 1308 is shown to include a diagnostics module 1332, diagnosticsresults 1334, and log data 1336. Diagnostics module 1332 can beconfigured to perform a diagnostic test of building device 1300.Diagnostic tests can include, for example, a span or range test, aforce/torque test, a calibration test, a failure modes test, atiming/speed test, or any other type of diagnostic test that can beperformed by building device 1300. Results of the diagnostic tests canbe stored in memory 1308 as diagnostics results 1334. Diagnosticsresults 1334 can be communicated to an external system or device (e.g.,a system controller, a field controller, an economizer controller, aclient device, a factory or laboratory diagnostics system, etc.) via NFCcircuit 1310. In some embodiments, results of the diagnostic test can beanalyzed by processor 1106 and the analysis of the results of thediagnostic test can be communicated to an external system or device(e.g., a system controller, a field controller, an economizercontroller, a client device, a factory or laboratory diagnostics system,etc.) via NFC circuit 1310.

Log data 1336 can include any information related to the operation ofbuilding device 1300. For example, log data 1336 can include buildingdevice positions, control signal values, feedback signal values, anamount of force or torque exerted by building device 1300, a measuredtemperature, or any other variable generated or used by building device1300. Log data 1336 can store information with time stamps indicating atime at which the stored values were used or observed by building device1300. Log data 1336 can be communicated to an external system or deviceto evaluate building device performance and/or to perform externaldiagnostics. In some embodiments, log data 1336 and/or diagnosticsresults 1334 include wired/wireless network information (e.g., networkdiagnostics, network logs, etc.). Network diagnostics can include, forexample, failed message sends, a number of retries for failed messagesends, network connectivity diagnostics, or any other type of diagnosticresult pertaining to network configuration. Network logs can include,for example, a communications channel used by communications interface1314, a wired/wireless network ID, a communications protocol, networkaddress settings, or any other type of log information pertaining tonetwork settings and/or connectivity.

Still referring to FIG. 13, building device 1300 is shown to include acommunications interface 1314. In some embodiments, communicationsinterface 1314 is a wired communications interface which is used bybuilding device 1300 to communicate with a controller (e.g., controller100, described with reference to FIGS. 2-6), another building device, orto an external system or device. In other embodiments, communicationsinterface 1314 is a wireless communications interface (e.g., wirelesstransceiver) which is used by building device 1300 to communicate with acontroller (e.g., controller 100, described with reference to FIGS.2-6), another building device, or to an external system or device.

Communications interface 1314 can be configured to facilitatebidirectional data communications between processing circuit 1302 and anexternal device. Wireless transceiver can be used by processing circuit1302 to transmit data stored in memory 1308 to the external deviceand/or to receive data from the external device.

Data communicated via communications interface 1314 can include, forexample, sensor data collected by transducer 1304 or actuator controlsignal for transducer 1304. Processing circuit 1302 can retrieve datafrom memory 1308 and transmit the retrieved data to the external devicevia communications interface 1314. Processing circuit 1302 can receivedata from the external device via communications interface 1314 andstore the received data in memory 1308. In other embodiments, transducer1304 and communications interface 1314 can communicate directly, withoutprocessing circuit 1302.

Communications interface 1314 can utilize any of a variety of wirelesstechnologies and/or communications protocols for wireless datacommunications. For example, Communications interface 1314 can use anyappropriate protocol, such as LON, BACnet, Bluetooth, Bluetooth lowenergy (BLE), WiFi, WiFi direct, Zigbee, radio frequency communication(e.g., RFID, radio waves, etc.), optical communication, electromagneticsignals, sound transmission, or any other wireless communicationstechnology to communicate with other building devices.

Communications interface 1314 can be configured to operate in a poweredmode or a non-powered mode. In the powered mode, communicationsinterface 1314 can receive power from another energy source (e.g., awired power connection, an on-board source 1312, etc.). In thenon-powered mode, communications interface 1314 can draw power from anelectromagnetic field, wave, or radiation using an antenna or receptor.Communications interface 1314 can use any of a variety of wirelessenergy transfer technologies (e.g., electrodynamic induction,electrostatic induction, lasers, microwaves, etc.) to obtain or harvestenergy wirelessly. Advantageously, communications interface 1314 allowsbuilding device 1300 to engage in bidirectional wireless datacommunications without requiring a wired power or data connection to anexternal device.

Referring now to FIG. 14, NFC circuit 1310 is shown in more detail,according to some embodiments. NFC circuit 1310 includes an NFC chip1400. NFC chip 1400 can be, for example, an M24LR series NFC chip,marketed by STMicroelectronics. According to some embodiments, NFC chip1400 includes a Vout pin 1402, antenna coil (AC0, AC1) pins 1404 and1406, a Vcc pin 1408, a serial data (SDA) pin 1410, a serial clock (SCL)pin 1412, an RF WIP/BUSY pin 1414, and a Vcc pin 1416.

AC0 pin 1404 and AC1 pin 1406 are coupled to a pick-up antenna 1418.Antenna 1418 forms an inductive loop and is configured to inductivelycouple NFC chip 1400 to the external device (e.g., mobile device 1340).Antenna 1418 can be any conductive member formed in the shape of a loop.For example, antenna 1418 can be formed by a trace of a conductivematerial (e.g., copper) on a printed circuit board, or a trace on a chipantenna. In some embodiments, antenna 1418 can be formed as a trace on aflexible member (e.g., a flexible printed circuit board) to reduce thesize of NFC circuit 1310 and facilitate the packaging of NFC circuit1310 in building device 1300. Data can be exchanged between NFC chip1400 and the external device and power can be received by NFC chip 1400from the external device via AC pin 1404 and AC1 pin 1406.

Vss pin 1408 is connected to ground 1420. Power is received by NFC chip1400 from the electromagnetic field generated by the external device viaantenna 1418. Antenna 1418 can be configured to draw power from awireless signal in the form of an alternating magnetic or electricfield. The field can be produced by mobile device 1340 or anotherexternal device. In some embodiments, the magnetic or electric field isa NFC field (i.e., an alternating magnetic field with a frequency ofapproximately 13.56 MHz, compatible with near field communications (NFC)devices). The magnetic field can induce a voltage in antenna 1418. Insome embodiments, NFC circuit 1410 stores energy derived from thewireless signal using one or more capacitors.

By harvesting power from the electromagnetic field generated by theexternal device, no power connection is needed between processingcircuit 1302 and NFC chip 1400. If building device 1300 is a wirelessdevice powered by an on-board power source 1312, this allows NFC chip1400 to operate without decreasing the life of on-board power source1312. In some embodiments, power can be received by NFC chip 1400 fromanother device via Vcc pin 1416. In some embodiments, power can besupplied from NFC chip 1400 to another device via Vout pin 1402.

Advantageously, NFC circuit 1310 can be configured to provide power toprocessing circuit 1302 and communications interface 1314 using thepower drawn from the wireless signal received at antenna 1418. Thisadvantage allows building device 1300 to engage in bidirectionalcommunications with an external device regardless of whether buildingdevice 1300 receives power from a wired power connection. For example,building device 1300 can communicate with external devices whilebuilding device 1300 is still in its packaging at a manufacturerfacility or a distributor location. Building device 1300 can beconstructed and packaged as a generic building device and subsequentlyconfigured with suitable firmware, software, configuration parameters(e.g., timing, DA/RA, etc.), or other data specific to a particularbuilding device model and/or implementation. Building device 1300 canalso communicate with external devices when installed or uninstalled.For example, diagnostic information can be read from building device1300 by an external device via NFC when in a factory or distributionfacility to determine faulty units, in the field, or in a lab afterbuilding device 1300 has been removed and replaced (e.g., due tomalfunction or failure).

NFC chip 1400 is coupled to processing circuit 1302 via aninter-integrated circuit (I2C) bus 1422. I2C bus 1422 includes an SDAline 1424 connecting SDA pin 1410 to a universal asynchronousreceiver/transmitter (UART) port 1428 of processing circuit 1302 and anSCL line 1426 connecting SCL pin 1410 to UART port 1428. SDA line 1424is a bi-directional data line configured for the transfer of databetween processing circuit 1302 and NFC chip 1400. SCL line 1426 is aunidirectional signal line configured for the transfer of a synchronousclock signal from processing circuit 1302 to NFC chip 1400. Processingcircuit 1302 is configured to allow NFC chip 1400 to access and modifyvarious data stored in memory 1308, including, for example, networkaddresses, model numbers, manufacturing date codes, firmware forprocessing circuit 1302, wireless network diagnostic information, sensorinput values (e.g., switch settings, temperature readings, RH readings,PIR sensor readings, button states, etc.), setpoint adjustments, modelconfiguration data (e.g., torque, travel time, transducer calibration,etc.), field parameters (e.g., DA/RA, span, offset, flow limitation,etc.), and/or any other type of data that can be communicated via NFCcircuit 1310.

NFC chip 1400 is further coupled to processing circuit 1302 via an RFWIP/BUSY line 1430. RF WIP/BUSY line 1430 connects RF WIP/BUSY pin 1414to an I/O port 1429 of processing circuit 1302. An RF WIP/BUSY signalcan be transmitted from NFC chip 1400 to processing circuit 1302 over RFWIP/BUSY line 1430 to provide a timing and flow control mechanism forprocessing circuit 1302. The RF WIP/Busy signal can facilitate timing ofdata transfer between processing circuit 1302 and NFC chip 1400.

In some embodiments, NFC circuit 1310 can be configured to change thebehavior of processing circuit 1302. For example, processing circuit1302 can operate in a non-powered or low-power mode. Upon establishing awireless communications connection with an external device, NFC circuit1310 can transmit a wake up signal to processing circuit 1302. Thesignal wakes up processing circuit 1302 from the non-powered orlow-power mode to draw power from a power source, such as on-board powersource 1312, thereby reducing the power drawn from NFC circuit 1310.Waking processing circuit 1302 to draw power from on-board power source1312 can be advantageous if insufficient power is harvested by NFCcircuit 1310 from the electromagnetic field generated by the externaldevice to operate processing circuit 1302.

In some embodiments, building device 1300 can communicate with externaldevices while building device 1300 is still in its packaging at amanufacturer facility or a distributor location. Building device 1300can be constructed and packaged as a generic device and subsequentlyconfigured with suitable firmware, software, configuration parameters,or other data specific to a particular building device model and/orimplementation. For example, a model number can be written to memory1308 including feature flags. The feature flags can be subsequentlyutilized to activate desired parameters and sensing elements (e.g.,transducer 1304). Operational data such as end of line test data orother diagnostic data can be extracted from building device 1300 withoutrequiring a physical data connection.

Referring again to FIG. 13, mobile device 1340 can include a deviceinterface application 1350. Device interface application 1350 providesuser-end functionality by providing the user with a visual interface toview the data communicated via NFC circuit 1310. Device interfaceapplication 1350 is configured to display to a user all relevantinformation related to building device 1300 and provide the user with ameans to easily view and change values for building device 1300. In someembodiments, device interface application 1350 can be activated manuallyby a user and can activate the NFC system of mobile device 1340 tofacilitate near field communication between building device 1300 andmobile device 1340 if mobile device 1340 is brought into close proximity(e.g., within 4 cm) of building device 1300. In some embodiments, deviceinterface application 1350 can be launched automatically if mobiledevice 1340 is brought into close proximity of building device 1300. Insome embodiments, device interface application can allow a user to viewall relevant information related to building device, but may requireadditional login credentials (e.g., password, user name, biometric data,etc.) to make changes to values for building device 1300.

Using an external device (e.g., mobile device 1340) with deviceinterface application 1350, a user can perform various upgrade, dataacquisition, and maintenance activities related to building devices1300. For example, a user can perform field upgrades andfield-configurations without physically interacting with building device1300 (e.g., opening a case to access physical dip-switches, making awired connection between the external device and building device 1300,manipulating a user interface of building device 1300, etc.). Thefunctionality provided by the wireless connection between buildingdevice 1300 and the external device can be advantageous if buildingdevice 1300 is installed in a hard to reach location.

Referring now to FIGS. 15A-15G, a graphical user interface (GUI) 1500for a device interface application 1350 is shown according to someembodiments. Referring to FIG. 15A, device interface application 1350 islaunched using an icon, widget, menu selection, or other launch object1502. In some embodiments, device interface application 1350 is launchedautomatically when the external device is brought into close proximitywith an appropriate building device, which is detected by the NFC chipof the external device.

Referring now to FIG. 15B, in some embodiments, once application 1350 islaunched and near field communication is established between theexternal device and the building device, a configuration screen 1504 ispresented to the user. In some embodiments, configuration screen 1504displays configuration parameters 1506 associated with the buildingdevice. For example, for a building device embodied as an actuator,configuration parameters 1506 can include model 1508, torque 1510, types1512, speed 1514, etc. A user can select the desired configurationparameter from a drop down list.

Referring now to FIG. 15C, in some embodiments, configuration screen1504 includes a current configuration display 1520. Currentconfiguration display 1520 includes current configuration parameters ofthe building device, which are read by the external device via NFC. Forexample, current configuration display 1520 can include information atag identification number 1522, memory block data 1524, currentparameters 1526 (e.g., model, torque, types, speed, etc.), and the timeand date 1528 of the last changes to the building device parameters.

Once the desired configuration parameters are selected by the user, theconfiguration parameters are transmitted to the building device (e.g.,transmitted over NFC and stored in memory). For example, theconfiguration parameters can be transmitted to the building device byselecting a write button 1516, or can be transmitted to the buildingdevice along with an instruction to lock the configuration parameters byselecting a write and lock button 1518. Locking a configurationparameter may require a user to enter authentication credentials (e.g.,password, user name, biometric data, etc.) to make further changes tothe configuration parameter. Current configuration display 1520 can beupdated after the user has written the data to the building device(e.g., by selecting write button 1516 or write and lock button 1518) toallow the user to confirm that the correct data has been transmitted tothe building device. In some embodiments, current configuration display1520 can include an indication (e.g., a checkmark, a ticked box, apadlock icon, etc.) to indicate if a particular parameter has beenlocked in a previous action. The parameters presented in currentconfiguration display 1520 may vary based on the type of building device(e.g., actuator, sensor, controller, etc.).

Referring now to FIG. 15D, upon receiving instructions to write data tothe building device (e.g., by the user selecting write button 1516 orwrite and lock button 1518), a status display 1530 can be presented tothe user. Status display 1530 indicates to the user if data is beingwritten from the external device to the building device or if data isbeing read from the building device by the external device. In someembodiments, status display 1530 can provide instructions 1532 to theuser. For example, instructions 1532 can instruct the user to positionthe external device in close proximity of the building device. In someembodiments, status display 1530 provides feedback to the user toindicate whether the requested operation (e.g., reading or writing)completes successfully or fails

Referring now to FIG. 15E, a user can access other modes of application1350 through a pop-up menu 1540. Pop-up menu 1540 includes a variety ofmodes of operation, such as a logging mode, a reporting mode, and a helpmode.

Referring to FIG. 15F, in some embodiments, help mode includesinstructions, such as text tutorials, visual tutorials, and videotutorials. A menu 1544 includes options for multiple help topics, suchas a NFC Read option 1546 and a NFC Write option 1548. Playback ornavigation controls 1555 are provided to allow a user to navigate (e.g.,scroll, play, skip, etc.) the presented help materials. In someembodiments, the help mode includes documentation specific to thebuilding device. Hyperlinks can be stored in memory in the buildingdevice or in the device interface application 1350. The hyperlink can beused to access product manuals, installation manuals or order forms.

Referring now to FIG. 15G, in some embodiments, in a logging mode, alogging screen 1550 is presented to the user. The logging mode allowsthe user to read data from the building device. Logging screen 1550includes log entries 1552 corresponding to reading and writingoperations for the building device. In some embodiments, log entries1552 includes a timestamp, a tag identification number, configurationparameters (e.g., model, torque, types, speed, etc.), action performed(e.g., reading or writing), whether the action was successful or failed,and error or troubleshooting messages (e.g., invalid parameter input).In some embodiments, log entries include a visual representation of thebuilding device. In some embodiments, the user can select the range oflog entries presented, for example, all entries over a defined timeperiod (e.g., entries from the previous month) or a defined number ofprevious entries (e.g., past 5 entries). In some embodiments, a pop-upmenu 1554 is presented to the user with additional options, such as aclear all option and a save and mail option. The clear all option allowsthe user to clear all log entries 1552. The save and mail option allowsthe user to save all or a portion of log entries 1552 and send them toanother device. For example, a user can be allowed to send log entries1552 to a desktop computer, a central server, a mail recipient, etc.

In some embodiments, a logging mode can be utilized to analyze data fromthe building device over a period of time. For example, information canbe logged and time stamped in the building device and a trend can beplotted on the external device. In some embodiments, the external deviceis left in close proximity to the actuator and to gather data atperiodic intervals to determine a trend.

Referring to FIG. 15H, in some embodiments, a detailed parameters window1556 is shown when a log entry 1552 is selected. Detailed parameterwindow 1556 presents additional information to the user, such asindividual memory block data. The information presented in detailedparameter window 1556 can be transmitted with the information presentedin log entries 1552 when log entries are transmitted to another device.

In some embodiments, device interface application 1350 includes featuresdirected towards a specific type of building device or feature of thebuilding device. In some embodiments, the building devices are installedin a master/slave configuration. The external device can automaticallyestablish which device is the master and which devices are slaves viaNFC. In some embodiments, a building device is placed into a manualoverride mode during commissioning. The building device can be placed ina manual override mode while the device is powered or unpowered. Thebuilding device can also be placed into a commissioning override modewhen powered to place the device at set points. In some embodiments, thedevice interface application 1350 is configured for use with a heatexchanger. The external device can trend temperature and drive the uniton the valve in step change. A temperature sensor on the external devicecan detect changes of temperature based on changes of valve opening.

Referring now to FIG. 10, a flowchart of a process 1600 for configuringand communicating with a building device is shown, according to someembodiments. In some embodiments, process 1600 is performed by aprocessing circuit of a building device. For example, process 1600 canbe performed by processing circuit 1302 of building device 1300, asdescribed with reference to FIGS. 13-15H.

Process 1600 is shown to include establishing a bidirectional near fieldcommunications (NFC) link between the building device and a mobiledevice via a NFC circuit of the building device (step 1602). The NFClink can be established automatically if the mobile device is broughtwithin a minimum distance (e.g., 4 inches) from the building device. TheNFC link can be initiated via a command from an application being run onthe mobile device.

Process 1600 is shown to include wirelessly transmitting data stored ina memory of the building device to the mobile device via the NFC circuit(step 1604). The data stored in a memory of the building device andwirelessly transmitted to the mobile device via the NFC circuit can bean access log entry. The log entry can include a variety of information,such as a timestamp, a tag identification number, a configurationparameter, a type of action performed, or a troubleshooting message.

Process 1600 is shown to include wirelessly receiving data from themobile device via the NFC circuit (step 1606). The data wirelesslyreceived from the mobile device via the NFC circuit, and stored in thememory of the building device can include configuration parametersassociated with the building device. For example, if the building deviceis an actuator, the configuration parameters can include a model, atorque, an actuator type, and a speed.

Process 1600 is shown to include storing the data received from themobile device in the memory of the building device (step 1608). In someembodiments, data received from the mobile device can be stored in themodel identification parameter module of the memory.

Configuration of Exemplary Embodiments

Embodiments of the subject matter and the operations described in thisspecification can be implemented in digital electronic circuitry, or incomputer software embodied on a tangible medium, firmware, or hardware,including the structures disclosed in this specification and theirstructural equivalents, or in combinations of one or more of them.Embodiments of the subject matter described in this specification can beimplemented as one or more computer programs, i.e., one or more modulesof computer program instructions, encoded on one or more computerstorage medium for execution by, or to control the operation of, dataprocessing apparatus. Alternatively or in addition, the programinstructions can be encoded on an artificially-generated propagatedsignal, e.g., a machine-generated electrical, optical, orelectromagnetic signal, that is generated to encode information fortransmission to suitable receiver apparatus for execution by a dataprocessing apparatus. A computer storage medium can be, or be includedin, a computer-readable storage device, a computer-readable storagesubstrate, a random or serial access memory array or device, or acombination of one or more of them. Moreover, while a computer storagemedium is not a propagated signal, a computer storage medium can be asource or destination of computer program instructions encoded in anartificially-generated propagated signal. The computer storage mediumcan also be, or be included in, one or more separate components or media(e.g., multiple CDs, disks, or other storage devices). Accordingly, thecomputer storage medium can be tangible and non-transitory.

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources.

The term “client or “server” include all kinds of apparatus, devices,and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includespecial purpose logic circuitry, e.g., an FPGA (field programmable gatearray) or an ASIC (application-specific integrated circuit). Theapparatus can also include, in addition to hardware, code that createsan execution environment for the computer program in question, e.g.,code that constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may correspond to a file in a file system. A program can bestored in a portion of a file that holds other programs or data (e.g.,one or more scripts stored in a markup language document), in a singlefile dedicated to the program in question, or in multiple coordinatedfiles (e.g., files that store one or more modules, sub-programs, orportions of code). A computer program can be deployed to be executed onone computer or on multiple computers that are located at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto-optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), to name just a few.Devices suitable for storing computer program instructions and datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube), LCD (liquidcrystal display), OLED (organic light emitting diode),TFT (thin-filmtransistor), plasma, other flexible configuration, or any other monitorfor displaying information to the user and a keyboard, a pointingdevice, e.g., a mouse, trackball, etc., or a touch screen, touch pad,etc., by which the user can provide input to the computer. Other kindsof devices can be used to provide for interaction with a user as well;for example, feedback provided to the user can be any form of sensoryfeedback, e.g., visual feedback, auditory feedback, or tactile feedback;and input from the user can be received in any form, including acoustic,speech, or tactile input. In addition, a computer can interact with auser by sending documents to and receiving documents from a device thatis used by the user; for example, by sending web pages to a web browseron a user's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back-end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an embodiment of the subjectmatter described in this specification, or any combination of one ormore such back-end, middleware, or front-end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network (“LAN”) and a widearea network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

While this specification contains many specific embodiment details,these should not be construed as limitations on the scope of anyinventions or of what can be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features can be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination can be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingcan be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product embodiedon a tangible medium or packaged into multiple such software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain embodiments, multitasking and parallel processingcan be advantageous.

The background section is intended to provide a background or context tothe invention recited in the claims. The description in the backgroundsection can include concepts that could be pursued, but are notnecessarily ones that have been previously conceived or pursued.Therefore, unless otherwise indicated herein, what is described in thebackground section is not prior art to the description or claims and isnot admitted to be prior art by inclusion in the background section.

What is claimed is:
 1. A method of configuring an actuator using amobile device, the method comprising: transmitting a plurality of firstconfiguration parameters usable by a control program of an actuator tocontrol operation of the actuator from the actuator to a mobile devicevia near field communication (NFC) using power drawn from an NFC signal,wherein the actuator is configured to couple to and control theoperation of a fluid control valve within an HVAC system; receiving theplurality of first configuration parameters associated with the actuatorat the mobile device and via NFC; displaying at least a portion of theplurality of first configuration parameters on a user interface of themobile device; transmitting a plurality of second configurationparameters associated with the actuator to the actuator via NFC; whereinthe plurality of first configuration parameters and the plurality ofsecond configuration parameters each comprises an actuation span for theactuator.
 2. The method of claim 1, wherein the plurality of first orsecond configuration parameters includes at least one of a set point, atravel time, and an operational mode, the operational mode identifyingone of a direct action mode and a reverse action mode.
 3. The method ofclaim 1, wherein the plurality of first or second configurationparameters includes at least two of a set point, a travel time, and anoperational mode, the operational mode identifying one of a directaction mode and a reverse action mode.
 4. The method of claim 1, whereinthe plurality of first or second configuration parameters includes a setpoint, a travel time, and an operational mode, the operational modeidentifying one of a direct action mode and a reverse action mode. 5.The method of claim 1, wherein the plurality of first or secondconfiguration parameters includes at least one of a building devicetype, a device identification, and a network address.
 6. The method ofclaim 1, further comprising displaying a visual representation of theactuator on the user interface.
 7. The method of claim 1, furthercomprising displaying a hyperlink on the user interface, the hyperlinkselectable to direct a user to additional information regarding theactuator.
 8. The method of claim 1, further comprising: receiving aconfiguration parameter update at the mobile device, the configurationparameter update replacing or modifying at least one of the plurality offirst configuration parameters; displaying the configuration parameterupdate on the user interface of the mobile device; and providing anindication on the user interface that the configuration parameter updatewas transmitted successfully to the actuator.
 9. The method of claim 1,further comprising displaying diagnostic data regarding the operation ofthe actuator.
 10. The method of claim 9, wherein the diagnostic dataincludes failure mode data.
 11. An application for configuring abuilding device of an HVAC system, the application being for executionon a mobile device comprising a user interface, the applicationcomprising instructions for: receiving a plurality of firstconfiguration parameters usable by a control program to controloperation of the building device from the building device via near fieldcommunication (NFC), wherein signals from the mobile device via NFC aresufficient for powering transmission of the plurality of firstconfiguration parameters from the building device; displaying at least aportion of the plurality of first configuration parameters on the userinterface; and transmitting a plurality of second configurationparameters usable by the control program to control the operation of thebuilding device and specific to a particular implementation of thebuilding device to the building device via NFC; wherein the plurality offirst configuration parameters and the plurality of secondconfigurations parameters are associated with control of an actuatorconfigured to couple to and control the operation of a fluid controlvalve of an HVAC system.
 12. The application of claim 11, wherein theplurality of first or second configuration parameters includes at leastone of a set point, a travel time, and an operational mode, theoperational mode identifying one of a direct action mode and a reverseaction mode.
 13. The application of claim 11, wherein the plurality offirst or second configuration parameters includes at least one of abuilding device type, a device identifier, and a network address. 14.The application of claim 11, further comprising instructions fordisplaying a visual representation of the building device on the userinterface.
 15. The application of claim 11, further comprisinginstructions for displaying a hyperlink on the user interface, thehyperlink selectable to direct a user to additional informationregarding the building device.
 16. The application of claim 11, furthercomprising instructions for: receiving a configuration parameter update,the configuration parameter update replacing or modifying at least oneof the plurality of first configuration parameters; transmitting theconfiguration parameter update to the building device via NFC; andproviding an indication that the modified at least one of theconfiguration parameters was transmitted successfully to the buildingdevice.
 17. The application of claim 11, further comprising instructionsfor displaying diagnostic data regarding the operation of the buildingdevice.
 18. The application of claim 16, further comprising instructionsfor displaying the configuration parameter update on the user interface.19. A mobile device for configuring a building device of an HVAC system,comprising: a user interface; and a processor configured to: receive aplurality of first configuration parameters associated with the buildingdevice from the building device via near field communication (NFC),wherein signals from the mobile device via NFC are sufficient forpowering transmission of the plurality of first configuration parametersfrom the building device; display at least a portion of the plurality offirst configuration parameters on the user interface; and transmit aplurality of second configuration parameters associated with thebuilding device to the building device via NFC; wherein the plurality offirst configuration parameters and the plurality of secondconfigurations parameters are associated with control of an actuatorconfigured to couple to and control operation of a fluid control valveof an HVAC system.
 20. The mobile device of claim 19, wherein theplurality of first configuration parameters or the plurality of secondconfiguration parameters are a plurality of operational parameters ofthe building device.
 21. The mobile device of claim 19, wherein theprocessor is further configured to receive data associated with at leastone of diagnosis and operation of the building device, the data receivedfrom the building device using NFC, wherein the data includes at leastone of timing data and speed data.
 22. The mobile device of claim 21,wherein the data includes failure mode data.
 23. The mobile device ofclaim 19, wherein the building device includes a flow sensor.
 24. Themobile device of claim 21, wherein the processor is configured todisplay the data on the user interface.
 25. The mobile device of claim19, wherein the processor is further configured to receive a user inputmodifying at least one of the plurality of first configurationparameters and transmit the modified at least one of the plurality offirst configuration parameters to the building device via directwireless communication between the mobile device and the building deviceas the plurality of second configuration parameters.
 26. The mobiledevice of claim 19, wherein the plurality of first configurationparameters and the plurality of second configuration parameters includea set point for the building device.
 27. A device interface applicationfor a mobile device and for use with a building device, the deviceinterface application comprising instructions causing the mobile deviceto: receive a plurality of first configuration parameters usable by acontrol program to control operation of the building device from thebuilding device using near field communication (NFC), wherein signalsfrom the mobile device via NFC are sufficient for powering transmissionof the plurality of first configuration parameters from the buildingdevice; display the plurality of first configuration parameters on auser interface; receive a configuration parameter update modifying orreplacing at least one of the plurality of first configurationparameters; and transmit the configuration parameter update as aplurality of second configuration parameters usable by the controlprogram to control the operation of the building device to the buildingdevice via NFC; wherein the plurality of first configuration parametersand the plurality of second configurations parameters are associatedwith control of an actuator configured to couple to and controloperation of a fluid control valve of an HVAC system.
 28. The deviceinterface application of claim 27, wherein the instructions furthercause the mobile device to display data associated with the operation ofthe building device, the data received from the building device via NFC.29. The device interface application of claim 27, wherein the pluralityof first or second configuration parameters include at least one of aset point, a travel time, and an operational mode, the operational modeidentifying one of a direct action mode and a reverse action mode. 30.The device interface application of claim 27, wherein the instructionsfurther cause the mobile device to display the plurality of secondconfiguration parameters on the user interface and provide an indicationon the user interface that the plurality of second configurationparameters were transmitted successfully to the building device.
 31. Themethod of claim 1, further comprising receiving the plurality of secondconfiguration parameters associated with the actuator at the actuatorvia NFC using the power drawn from the NFC signal, the plurality ofsecond configurations including an update to at least one of theplurality of first configuration parameters usable by the controlprogram to control the operation of the actuator.